From 41b5de87692b8262fbdbff7faab93f04ff0be453 Mon Sep 17 00:00:00 2001 From: Ivan Molodetskikh Date: Tue, 10 Feb 2026 17:57:52 +0300 Subject: [PATCH] Change all links from YaLTeR/niri to niri-wm/niri --- .github/ISSUE_TEMPLATE/config.yml | 4 ++-- CONTRIBUTING.md | 4 ++-- Cargo.toml | 2 +- docs/hooks/shortcodes.py | 2 +- docs/mkdocs.yaml | 4 ++-- docs/wiki/Configuration:-Introduction.md | 2 +- docs/wiki/Development:-Design-Principles.md | 2 +- docs/wiki/Development:-Documenting-niri.md | 4 ++-- docs/wiki/FAQ.md | 10 +++++----- docs/wiki/Getting-Started.md | 2 +- docs/wiki/IPC.md | 4 ++-- docs/wiki/Integrating-niri.md | 4 ++-- docs/wiki/Packaging-niri.md | 2 +- docs/wiki/README.md | 4 ++-- docs/wiki/Xwayland.md | 2 +- flake.nix | 4 ++-- niri-config/src/binds.rs | 2 +- niri-ipc/README.md | 2 +- niri.spec.rpkg | 2 +- resources/default-config.kdl | 12 ++++++------ src/backend/tty.rs | 6 +++--- src/handlers/layer_shell.rs | 2 +- src/niri.rs | 2 +- 23 files changed, 42 insertions(+), 42 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml index d1ceced5..5d00bda6 100644 --- a/.github/ISSUE_TEMPLATE/config.yml +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -1,9 +1,9 @@ contact_links: - name: Feature request - url: https://github.com/YaLTeR/niri/discussions/new?category=ideas + url: https://github.com/niri-wm/niri/discussions/new?category=ideas about: Ideas for new features and functionality (start a Discussion) - name: Ask a question - url: https://github.com/YaLTeR/niri/discussions/new?category=q-a + url: https://github.com/niri-wm/niri/discussions/new?category=q-a about: Question about niri (start a Discussion) - name: Matrix room url: https://matrix.to/#/#niri:matrix.org diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e118b5fa..1fd51aaa 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -31,7 +31,7 @@ I would really appreciate help with testing and reviewing them. ### Testing Pick a pull request you like, then build it and give it a go. -The [Developing niri wiki page](https://yalter.github.io/niri/Development:-Developing-niri) has guidance on running niri test builds. +The [Developing niri wiki page](https://niri-wm.github.io/niri/Development:-Developing-niri) has guidance on running niri test builds. Be really thorough with your testing. We're striving for polished features in niri, so point out any issues and bugs, even small ones like animation jank. @@ -84,7 +84,7 @@ When creating pull requests, please keep the following in mind. - When working on bigger features, I usually start with a big messy commit, then gradually split out smaller self-contained changes from it as the code gets into shape. - [git-rebase.io](https://git-rebase.io/) is a helpful guide for splitting commits and cleaning up history in git. - When you address a review comment, mark it as resolved. -- Remember to [run tests](https://yalter.github.io/niri/Development:-Developing-niri#tests) and format the code with `cargo +nightly fmt --all`. +- Remember to [run tests](https://niri-wm.github.io/niri/Development:-Developing-niri#tests) and format the code with `cargo +nightly fmt --all`. - For new layout actions, remember to add them to the randomized tests. For weird Wayland handling, adding client-server tests in `src/tests/` could be very useful. - Test your changes by hand thoroughly, including for edge cases and weird interactions. See the Testing section above for some tips. - Remember to document new config options on the wiki. diff --git a/Cargo.toml b/Cargo.toml index 622478e4..b19b3646 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -11,7 +11,7 @@ description = "A scrollable-tiling Wayland compositor" authors = ["Ivan Molodetskikh "] license = "GPL-3.0-or-later" edition = "2021" -repository = "https://github.com/YaLTeR/niri" +repository = "https://github.com/niri-wm/niri" rust-version = "1.85" [workspace.dependencies] diff --git a/docs/hooks/shortcodes.py b/docs/hooks/shortcodes.py index 66f5c43e..98a1c61a 100644 --- a/docs/hooks/shortcodes.py +++ b/docs/hooks/shortcodes.py @@ -40,5 +40,5 @@ def _badge_for_version(preposition: str, version: str): # we might fail to make real links to release notes on other cases too, but for now this is the one i've found return f"{preposition}: {version}" else: - path = f"https://github.com/YaLTeR/niri/releases/tag/v{version}" + path = f"https://github.com/niri-wm/niri/releases/tag/v{version}" return f"[{preposition}: {version}]({path})" diff --git a/docs/mkdocs.yaml b/docs/mkdocs.yaml index 3e33a92e..bfc3b364 100644 --- a/docs/mkdocs.yaml +++ b/docs/mkdocs.yaml @@ -1,7 +1,7 @@ site_name: niri docs_dir: wiki -site_url: https://yalter.github.io/niri -repo_url: https://github.com/YaLTeR/niri +site_url: https://niri-wm.github.io/niri +repo_url: https://github.com/niri-wm/niri edit_uri: edit/main/docs/wiki/ use_directory_urls: false diff --git a/docs/wiki/Configuration:-Introduction.md b/docs/wiki/Configuration:-Introduction.md index 28fa945e..e5c3a246 100644 --- a/docs/wiki/Configuration:-Introduction.md +++ b/docs/wiki/Configuration:-Introduction.md @@ -19,7 +19,7 @@ You can find documentation for various sections of the config on these wiki page ### Loading Niri will load configuration from `$XDG_CONFIG_HOME/niri/config.kdl` or `~/.config/niri/config.kdl`, falling back to `/etc/niri/config.kdl`. -If both of these files are missing, niri will create `$XDG_CONFIG_HOME/niri/config.kdl` with the contents of [the default configuration file](https://github.com/YaLTeR/niri/blob/main/resources/default-config.kdl), which are embedded into the niri binary at build time. +If both of these files are missing, niri will create `$XDG_CONFIG_HOME/niri/config.kdl` with the contents of [the default configuration file](https://github.com/niri-wm/niri/blob/main/resources/default-config.kdl), which are embedded into the niri binary at build time. Please use the default configuration file as the starting point for your custom configuration. The configuration is live-reloaded. diff --git a/docs/wiki/Development:-Design-Principles.md b/docs/wiki/Development:-Design-Principles.md index abb44e3e..7a3892a8 100644 --- a/docs/wiki/Development:-Design-Principles.md +++ b/docs/wiki/Development:-Design-Principles.md @@ -74,7 +74,7 @@ Here are some design considerations for the window layout logic. ## Default config -The [default config](https://github.com/YaLTeR/niri/blob/main/resources/default-config.kdl) is intended to give a familiar, helpful, and not too jarring experience to new niri users. +The [default config](https://github.com/niri-wm/niri/blob/main/resources/default-config.kdl) is intended to give a familiar, helpful, and not too jarring experience to new niri users. Importantly, it is not a "suggested rice config"; we don't want to startle people with full-on rainbow borders and crazy shaders. Since we're not a complete desktop environment (and don't have the contributor base to become one), we cannot provide a fully integrated experience—distro spins are better positioned to do this. diff --git a/docs/wiki/Development:-Documenting-niri.md b/docs/wiki/Development:-Documenting-niri.md index 34ac2dc1..93e7ccec 100644 --- a/docs/wiki/Development:-Documenting-niri.md +++ b/docs/wiki/Development:-Documenting-niri.md @@ -1,8 +1,8 @@ niri's documentation files are found in `docs/wiki/` and should be viewable and browsable in at least three systems: - The GitHub repo's markdown file preview -- [The GitHub repo's wiki](https://github.com/YaLTeR/niri/wiki) -- [The documentation site](https://yalter.github.io/niri/) +- [The GitHub repo's wiki](https://github.com/niri-wm/niri/wiki) +- [The documentation site](https://niri-wm.github.io/niri/) ## The GitHub repo's wiki diff --git a/docs/wiki/FAQ.md b/docs/wiki/FAQ.md index c2f597ee..edf7863d 100644 --- a/docs/wiki/FAQ.md +++ b/docs/wiki/FAQ.md @@ -66,14 +66,14 @@ I wouldn't be too surprised if, down the road, xwayland-satellite becomes the st ### Can I enable blur behind semitransparent windows? -Not yet, follow/upvote [this issue](https://github.com/YaLTeR/niri/issues/54). +Not yet, follow/upvote [this issue](https://github.com/niri-wm/niri/issues/54). -There's also [a PR](https://github.com/YaLTeR/niri/pull/1634) adding blur to niri which you can build and run manually. +There's also [a PR](https://github.com/niri-wm/niri/pull/1634) adding blur to niri which you can build and run manually. Keep in mind that it's an experimental implementation that may have problems and performance concerns. ### Can I make a window sticky / pinned / always on top / appear on all workspaces? -Not yet, follow/upvote [this issue](https://github.com/YaLTeR/niri/issues/932). +Not yet, follow/upvote [this issue](https://github.com/niri-wm/niri/issues/932). You can emulate this with a script that uses the niri IPC. For example, [nirius](https://git.sr.ht/~tsdh/nirius) seems to have this feature (`toggle-follow-mode`). @@ -82,7 +82,7 @@ For example, [nirius](https://git.sr.ht/~tsdh/nirius) seems to have this feature Firefox seems to first open the Bitwarden window with a generic Firefox title, and only later change the window title to Bitwarden, so you can't effectively target it with an `open-floating` window rule. -You'll need to use a script, for example [this one](https://github.com/YaLTeR/niri/discussions/1599) or other ones (search niri issues and discussions for Bitwarden). +You'll need to use a script, for example [this one](https://github.com/niri-wm/niri/discussions/1599) or other ones (search niri issues and discussions for Bitwarden). ### Can I open a window directly in the current column / in the same column as another window? @@ -92,7 +92,7 @@ Listen to the event stream for a new window opening, then call an action like `c Adding this directly to niri is challenging: - The act of "opening a window directly in some column" by itself is quite involved. Niri will have to compute the exact initial window size provided how other windows in a column would resize in response. This logic exists, but it isn't directly pluggable to the code computing a size for a new window. Then, it'll need to handle all sorts of edge cases like the column disappearing, or new windows getting added to the column, before the target window had a chance to appear. -- How do you indicate if a new window should spawn in an existing column (and in which one), as opposed to a new column? Different people seem to have different needs here (including very complex rules based on parent PID, etc.), and it's very unclear design-wise what kind of (simple) setting is actually needed and would be useful. See also https://github.com/YaLTeR/niri/discussions/1125. +- How do you indicate if a new window should spawn in an existing column (and in which one), as opposed to a new column? Different people seem to have different needs here (including very complex rules based on parent PID, etc.), and it's very unclear design-wise what kind of (simple) setting is actually needed and would be useful. See also https://github.com/niri-wm/niri/discussions/1125. ### Why does moving the mouse against a monitor edge focus the next window, but only sometimes? diff --git a/docs/wiki/Getting-Started.md b/docs/wiki/Getting-Started.md index e908c834..46801c68 100644 --- a/docs/wiki/Getting-Started.md +++ b/docs/wiki/Getting-Started.md @@ -34,7 +34,7 @@ Check the DankMaterialShell's [compositor setup page](https://danklinux.com/docs ## Slower and more considered start The easiest way to get niri is to install one of the distribution packages. -Here are some of them: [Fedora COPR](https://copr.fedorainfracloud.org/coprs/yalter/niri/) and [nightly COPR](https://copr.fedorainfracloud.org/coprs/yalter/niri-git/) (which I maintain myself), [NixOS Flake](https://github.com/sodiboo/niri-flake), and some more from repology below, including a [pacstall package](https://pacstall.dev/packages/niri/) for Debian-based distros. +Here are some of them: [Fedora COPR](https://copr.fedorainfracloud.org/coprs/niri-wm/niri/) and [nightly COPR](https://copr.fedorainfracloud.org/coprs/niri-wm/niri-git/) (which I maintain myself), [NixOS Flake](https://github.com/sodiboo/niri-flake), and some more from repology below, including a [pacstall package](https://pacstall.dev/packages/niri/) for Debian-based distros. See the [Building](#building) section if you'd like to compile niri yourself and the [Packaging niri](./Packaging-niri.md) page if you want to package niri. [![Packaging status](https://repology.org/badge/vertical-allrepos/niri.svg)](https://repology.org/project/niri/versions) diff --git a/docs/wiki/IPC.md b/docs/wiki/IPC.md index 813461d6..415ba2a6 100644 --- a/docs/wiki/IPC.md +++ b/docs/wiki/IPC.md @@ -26,7 +26,7 @@ To get a taste of the events, run `niri msg event-stream`. Though, this is more of a debug function than anything. You can get raw events from `niri msg --json event-stream`, or by connecting to the niri socket and requesting an event stream manually. -You can find the full list of events along with documentation [here](https://yalter.github.io/niri/niri_ipc/enum.Event.html). +You can find the full list of events along with documentation [here](https://niri-wm.github.io/niri/niri_ipc/enum.Event.html). ### Programmatic Access @@ -57,7 +57,7 @@ $ env NIRI_SOCKET=./temp.sock niri msg action focus-workspace 2 {"Action":{"FocusWorkspace":{"reference":{"Index":2}}}} ``` -You can find all available requests and response types in the [niri-ipc sub-crate documentation](https://yalter.github.io/niri/niri_ipc/). +You can find all available requests and response types in the [niri-ipc sub-crate documentation](https://niri-wm.github.io/niri/niri_ipc/). ### Backwards Compatibility diff --git a/docs/wiki/Integrating-niri.md b/docs/wiki/Integrating-niri.md index 6013f776..c619fb69 100644 --- a/docs/wiki/Integrating-niri.md +++ b/docs/wiki/Integrating-niri.md @@ -4,7 +4,7 @@ First, for creating a niri package, see the [Packaging](./Packaging-niri.md) pag ### Configuration Niri will load configuration from `$XDG_CONFIG_HOME/niri/config.kdl` or `~/.config/niri/config.kdl`, falling back to `/etc/niri/config.kdl`. -If both of these files are missing, niri will create `$XDG_CONFIG_HOME/niri/config.kdl` with the contents of [the default configuration file](https://github.com/YaLTeR/niri/blob/main/resources/default-config.kdl), which are embedded into the niri binary at build time. +If both of these files are missing, niri will create `$XDG_CONFIG_HOME/niri/config.kdl` with the contents of [the default configuration file](https://github.com/niri-wm/niri/blob/main/resources/default-config.kdl), which are embedded into the niri binary at build time. This means that you can customize your distribution defaults by creating `/etc/niri/config.kdl`. When this file is present, niri *will not* automatically create a config at `~/.config/niri/`, so you'll need to direct your users how to do it themselves. @@ -36,7 +36,7 @@ Make sure your system installer sets the keyboard layout via systemd-localed, an ### Autostart Niri works with the normal systemd autostart. -The default [niri.service](https://github.com/YaLTeR/niri/blob/main/resources/niri.service) brings up `graphical-session.target` as well as `xdg-desktop-autostart.target`. +The default [niri.service](https://github.com/niri-wm/niri/blob/main/resources/niri.service) brings up `graphical-session.target` as well as `xdg-desktop-autostart.target`. To make a program run at niri startup without editing the niri config, you can either link its .desktop to `~/.config/autostart/`, or use a .service file with `WantedBy=graphical-session.target`. See the [example systemd setup](./Example-systemd-Setup.md) page for some examples. diff --git a/docs/wiki/Packaging-niri.md b/docs/wiki/Packaging-niri.md index abc873f2..966638ab 100644 --- a/docs/wiki/Packaging-niri.md +++ b/docs/wiki/Packaging-niri.md @@ -47,7 +47,7 @@ Set them as automatically-installed optional dependencies, if possible. Working hardware acceleration is required for running niri. - Some notification daemon like `mako`, generally required for apps to work correctly. -Finally, you may want to auto-install some of the applications bound in niri's [default configuration file](https://github.com/YaLTeR/niri/blob/main/resources/default-config.kdl) (search for `spawn`), such as `alacritty` and `fuzzel`. +Finally, you may want to auto-install some of the applications bound in niri's [default configuration file](https://github.com/niri-wm/niri/blob/main/resources/default-config.kdl) (search for `spawn`), such as `alacritty` and `fuzzel`. ### Running tests diff --git a/docs/wiki/README.md b/docs/wiki/README.md index c9e424d0..d32f706f 100644 --- a/docs/wiki/README.md +++ b/docs/wiki/README.md @@ -4,9 +4,9 @@ Feel free to look through usage and [Getting started](./Getting-Started.md). If you're looking for ways to configure niri, check out the [introduction to configuration](./Configuration:-Introduction.md). If you'd like to help with niri, there are plenty of both coding- and non-coding-related ways to do so. -See [CONTRIBUTING.md](https://github.com/YaLTeR/niri/blob/main/CONTRIBUTING.md) for an overview. +See [CONTRIBUTING.md](https://github.com/niri-wm/niri/blob/main/CONTRIBUTING.md) for an overview. -If you're not already here, check out our new wiki website! https://yalter.github.io/niri/ +If you're not already here, check out our new wiki website! https://niri-wm.github.io/niri/ --- diff --git a/docs/wiki/Xwayland.md b/docs/wiki/Xwayland.md index a03e9a08..6b69a7cf 100644 --- a/docs/wiki/Xwayland.md +++ b/docs/wiki/Xwayland.md @@ -47,7 +47,7 @@ It will open as a new window. This method involves invoking XWayland directly and running it as its own window, it also requires an extra X11 window manager running inside it. -![Xwayland running in rootful mode.](https://github.com/YaLTeR/niri/assets/1794388/b64e96c4-a0bb-4316-94a0-ff445d4c7da7) +![Xwayland running in rootful mode.](https://github.com/niri-wm/niri/assets/1794388/b64e96c4-a0bb-4316-94a0-ff445d4c7da7) Here's how you do it: diff --git a/flake.nix b/flake.nix index 855d026b..39d55607 100644 --- a/flake.nix +++ b/flake.nix @@ -107,7 +107,7 @@ buildNoDefaultFeatures = true; # ever since this commit: - # https://github.com/YaLTeR/niri/commit/771ea1e81557ffe7af9cbdbec161601575b64d81 + # https://github.com/niri-wm/niri/commit/771ea1e81557ffe7af9cbdbec161601575b64d81 # niri now runs an actual instance of the real compositor (with a mock backend) during tests # and thus creates a real socket file in the runtime dir. # this is fine for our build, we just need to make sure it has a directory to write to. @@ -157,7 +157,7 @@ meta = { description = "Scrollable-tiling Wayland compositor"; - homepage = "https://github.com/YaLTeR/niri"; + homepage = "https://github.com/niri-wm/niri"; license = lib.licenses.gpl3Only; mainProgram = "niri"; platforms = lib.platforms.linux; diff --git a/niri-config/src/binds.rs b/niri-config/src/binds.rs index 98ac9fea..5b0efb97 100644 --- a/niri-config/src/binds.rs +++ b/niri-config/src/binds.rs @@ -1034,7 +1034,7 @@ impl FromStr for Key { // [0]: https://github.com/xkbcommon/libxkbcommon/blob/45a118d5325b051343b4b174f60c1434196fa7d4/src/keysym.c#L276 // [1]: https://docs.rs/xkbcommon/latest/xkbcommon/xkb/keysyms/index.html#:~:text=KEY%5FXF86ScreenSaver // - // See https://github.com/YaLTeR/niri/issues/1969 + // See https://github.com/niri-wm/niri/issues/1969 if keysym == Keysym::XF86_Screensaver { keysym = keysym_from_name(key, KEYSYM_NO_FLAGS); if keysym.raw() == KEY_NoSymbol { diff --git a/niri-ipc/README.md b/niri-ipc/README.md index 940ab650..7c8ba50f 100644 --- a/niri-ipc/README.md +++ b/niri-ipc/README.md @@ -1,6 +1,6 @@ # niri-ipc -Types and helpers for interfacing with the [niri](https://github.com/YaLTeR/niri) Wayland compositor. +Types and helpers for interfacing with the [niri](https://github.com/niri-wm/niri) Wayland compositor. ## Backwards compatibility diff --git a/niri.spec.rpkg b/niri.spec.rpkg index 8e91b428..ec256aff 100644 --- a/niri.spec.rpkg +++ b/niri.spec.rpkg @@ -60,7 +60,7 @@ SourceLicense: GPL-3.0-or-later License: ((MIT OR Apache-2.0) AND BSD-3-Clause) AND ((MIT OR Apache-2.0) AND Unicode-3.0) AND (0BSD OR MIT OR Apache-2.0) AND (Apache-2.0) AND (Apache-2.0 AND MIT) AND (Apache-2.0 OR BSL-1.0) AND (Apache-2.0 OR MIT) AND (Apache-2.0 OR MIT OR Unlicense) AND (Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT) AND (BSD-2-Clause) AND (BSD-2-Clause OR Apache-2.0 OR MIT) AND (BSD-3-Clause OR MIT OR Apache-2.0) AND (GPL-3.0-or-later) AND (ISC) AND (MIT) AND (MIT OR Apache-2.0) AND (MIT OR Apache-2.0 OR LGPL-2.1-or-later) AND (MIT OR Apache-2.0 OR Zlib) AND (MIT OR Zlib OR Apache-2.0) AND (MPL-2.0) AND (Unicode-3.0) AND (Unlicense OR MIT) AND (Zlib) AND (Zlib OR Apache-2.0 OR MIT) # LICENSE.dependencies contains a full license breakdown -URL: https://github.com/YaLTeR/niri +URL: https://github.com/niri-wm/niri VCS: {{{ git_dir_vcs }}} Source: {{{ git_dir_pack }}} diff --git a/resources/default-config.kdl b/resources/default-config.kdl index 808c0fb4..3fa09d56 100644 --- a/resources/default-config.kdl +++ b/resources/default-config.kdl @@ -1,11 +1,11 @@ // This config is in the KDL format: https://kdl.dev // "/-" comments out the following node. // Check the wiki for a full description of the configuration: -// https://yalter.github.io/niri/Configuration:-Introduction +// https://niri-wm.github.io/niri/Configuration:-Introduction // Input device configuration. // Find the full list of options on the wiki: -// https://yalter.github.io/niri/Configuration:-Input +// https://niri-wm.github.io/niri/Configuration:-Input input { keyboard { xkb { @@ -73,7 +73,7 @@ input { // by running `niri msg outputs` while inside a niri instance. // The built-in laptop monitor is usually called "eDP-1". // Find more information on the wiki: -// https://yalter.github.io/niri/Configuration:-Outputs +// https://niri-wm.github.io/niri/Configuration:-Outputs // Remember to uncomment the node by removing "/-"! /-output "eDP-1" { // Uncomment this line to disable this output. @@ -108,7 +108,7 @@ input { // Settings that influence how windows are positioned and sized. // Find more information on the wiki: -// https://yalter.github.io/niri/Configuration:-Layout +// https://niri-wm.github.io/niri/Configuration:-Layout layout { // Set gaps around windows in logical pixels. gaps 16 @@ -295,7 +295,7 @@ screenshot-path "~/Pictures/Screenshots/Screenshot from %Y-%m-%d %H-%M-%S.png" // Animation settings. // The wiki explains how to configure individual animations: -// https://yalter.github.io/niri/Configuration:-Animations +// https://niri-wm.github.io/niri/Configuration:-Animations animations { // Uncomment to turn off all animations. // off @@ -306,7 +306,7 @@ animations { // Window rules let you adjust behavior for individual windows. // Find more information on the wiki: -// https://yalter.github.io/niri/Configuration:-Window-Rules +// https://niri-wm.github.io/niri/Configuration:-Window-Rules // Work around WezTerm's initial configure bug // by setting an empty default-column-width. diff --git a/src/backend/tty.rs b/src/backend/tty.rs index a44009fc..259dde30 100644 --- a/src/backend/tty.rs +++ b/src/backend/tty.rs @@ -649,7 +649,7 @@ impl Tty { let device = self.devices.get_mut(&node).unwrap(); // Someone on an old device hit what seems to be a driver bug without this: - // https://github.com/YaLTeR/niri/issues/3048 + // https://github.com/niri-wm/niri/issues/3048 let force_disable = self .config .borrow() @@ -1677,8 +1677,8 @@ impl Tty { // This is an error!() because it shouldn't happen, but on some systems it somehow // does. Kernel sending rogue vblank events? // - // https://github.com/YaLTeR/niri/issues/556 - // https://github.com/YaLTeR/niri/issues/615 + // https://github.com/niri-wm/niri/issues/556 + // https://github.com/niri-wm/niri/issues/615 error!( "unexpected redraw state for output {name} (should be WaitingForVBlank); \ can happen when resuming from sleep or powering on monitors: {state:?}" diff --git a/src/handlers/layer_shell.rs b/src/handlers/layer_shell.rs index 8560970d..e0f1084f 100644 --- a/src/handlers/layer_shell.rs +++ b/src/handlers/layer_shell.rs @@ -155,7 +155,7 @@ impl State { // 2) Same-layer exclusive layer surfaces are already preferred to on-demand surfaces in // update_keyboard_focus(), so we don't need to check for that here. // - // https://github.com/YaLTeR/niri/issues/641 + // https://github.com/niri-wm/niri/issues/641 let on_demand = layer.cached_state().keyboard_interactivity == wlr_layer::KeyboardInteractivity::OnDemand; if was_unmapped && on_demand { diff --git a/src/niri.rs b/src/niri.rs index aef828f6..414f702d 100644 --- a/src/niri.rs +++ b/src/niri.rs @@ -311,7 +311,7 @@ pub struct Niri { // verified that a black single-pixel-buffer background lets the foreground surface to be // unredirected. // - // https://github.com/YaLTeR/niri/issues/619 + // https://github.com/niri-wm/niri/issues/619 #[cfg(test)] pub single_pixel_buffer_state: SinglePixelBufferState,