We've hit 15k stars on the niri repo!!   

#niri

Just merged Alt-Tab to main, shortly arriving at your nearest niri-git. Comes with plenty of ways to tweak it if you want [1], and a focus timestamp in the IPC [2] that lets shell devs make their own recent windows switchers.

[1]: https://yalter.github.io/niri/Configuration%3A-Recent-Windows.html
[2]: https://yalter.github.io/niri/niri_ipc/struct.Window.html#structfield.focus_timestamp

#niri

Did some work on the TTY backend in niri over the past few days. Merged PR for DisplayLink dock support, added "panel orientation" property read, and, based on cosmic-comp code, implemented the necessary logic to avoid screen blanking. Finally, both at niri startup and when switching TTYs, your screen won't flicker, as long as resolution/refresh rate stay the same.

Even when the screen does blank, it'll go faster, as there's now just one modeset instead of two (clear then draw frame).

#niri

Took some fighting but I think I've managed to teach the new Alt-Tab to speak to the screen reader

#niri

I finished and merged the horizontal drag interaction tweak from a previous post. It's very handy but can also be annoying when you want to move windows across monitors, so on mouse I restricted it to headerbar dragging (so, not Mod+LMB and not in the overview).

On touch however, it works for both headerbar dragging, and for Mod+Touch, so you can now easily scroll the view around.

I also added the thing where you can touch with another finger to switch between floating and tiling.

#niri

DankMaterialShell folks set up builds for Debian, Ubuntu and OpenSUSE, so now it's super easy to try niri & DMS on those systems.

I added Ubuntu commands to the niri quick start guide: https://yalter.github.io/niri/Getting-Started.html

Debian and OpenSUSE here: https://build.opensuse.org/project/show/home:AvengeMedia:danklinux

#niri

Today I'm releasing niri v25.11 with long-awaited config includes, Alt-Tab, true maximize, custom modes, and a bunch of other improvements!    Enjoy the release notes :)

https://github.com/YaLTeR/niri/releases/tag/v25.11

#niri #smithay #wayland #rust

Congrats sternenseemann on the nixpkgs niri any% WR at 3 h 20 min

https://github.com/NixOS/nixpkgs/pull/466213

#niri

funny how while working on alt-tab i discovered that mouse scrolling on top of the DMS bar switches workspaces, which completely replaced any need i had for alt-tab, so i ended up never using it

this DMS bar scrolling feature also removed one of my main usecases for the overview

and then the new horizontal window drag gesture removed my other main usecase for the overview, so now i'm opening the overview quite rarely too

(both have their uses; just curious to watch my own habits shift)

#niri

I've had one of those sessions today where I worked with a ton of random windows on a long workspace, while preparing slides for a uni scientific presentation. All kinds of various PDFs, file managers, InkScape, GIMP and so on.

Horizontal mouse headerbar drag to scroll the view was a lifesaver. Definitely a good choice adding this. Along with scrolling the view on DnD near the screen edge. Going through the overview, or always through the keyboard, would be very annoying.

#niri

yuxqiu just improved the default GPU detection logic in Smithay, so niri-git now works out of the box on Asahi and Pinephone devices, without having to manually configure render-drm-device!

#niri

i added the pointer warping thing from blender to when you drag the view around in niri with the mouse

hf with this new way to pass time during boring meetings

(on a more serious note this helps when you need to scroll further than the edge of your monitor allows)

also unrelated: merged optional config includes earlier today

#niri

on niri-git, the nautilus rename popup now works properly with IMEs running

(and generally popups with text fields should work now)

#niri

Experimenting with a restructure of the niri rendering code to uncurse it somewhat by getting rid of all complex impl Iterator chains and lifetimes, which also lets me remove some intermediate small Vecs. In essence, going from pull to push iteration.

I'm surprised that the result is consistently 2-3x faster than before. Wonder if it's the Vecs, or if inverting (massive) codegen'd iterators into a normal call stack passing a closure arg, providing the main benefit

#niri

Finished the push-based rendering refactor, made a write-up here for the curious: https://github.com/YaLTeR/niri/pull/3113

It even ended up with a negative delta (+762 -780) which is always a W.

Btw I ran the comparison on my Eee PC and there the difference is even more extreme, like 8x faster rendering list construction (which is once again only a part of the total rendering time, and notably doesn't include actual rendering, but still nice).

#niri

biblically accurate window management

#niri

i'm reviving the PR integrating Tracy GPU profiling into Smithay. Here are two test captures from niri: one for normal + screencast rendering, one for iGPU + dGPU monitor rendering

#niri

Looking for ideas on how to go about translating niri (the binary, and the wiki). If you have experience doing this with other FOSS projects, please share:

https://github.com/YaLTeR/niri/discussions/3135

#niri

Is there any good way of moving a process into a systemd StartTransientScope together with its children?

In niri we put spawned processes into scopes, so oomd and other stuff can work properly. Usually you do it by putting yourself into a scope, then exec-ing the target program. But that's a 7 ms toll on startup time, so in niri we spawn the program right away, and then put it into a scope. However, if the program forks fast enough, that child doesn't go into the scope..

#niri #linux #systemd

Turns out GNOME Shell has the same problem: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6565

I also wrote it down in a more detailed form on the niri issues for future reference: https://github.com/YaLTeR/niri/issues/3201

niri can now include the mouse pointer on window screenshots, a feature that had several more edge cases than I thought before starting to work on it (and it's likely not the ones you think, those ones were easy)

#niri

Merged another long time overdue niri PR: mouse cursor via metadata in PipeWire screencasts (lets you toggle Show Cursor on/off in OBS), and full mouse cursor support in window casts.

The cursor is visible only when the window is receiving mouse events—if you're moving the mouse on top of something else covering the target window, the cursor won't be (unintentionally) painted.

Thanks @abmantis for driving this, including debugging a memory bug in PW!

#niri

Working on a screencast IPC for niri. The idea is to give info to desktop bars to be able to add a screencast indicator whenever something is recording the screen.

Got it hooked up for both PipeWire (obviously) and wlr-screencopy. For the latter there's no good way to tell if something is a screencast so I went with some heuristics.

Here's the icon working on the DMS bar, as well as a popup with the full available info I made for debugging.  

#niri

Oh right, for PipeWire I can send the node ID, which DMS can then use to fetch the consumer application name!

#niri

The screencast IPC is now merged: https://yalter.github.io/niri/niri_ipc/struct.Cast.html

#niri

Also added niri msg action stop-cast to force-stop a PipeWire screencast

#niri

working on my new visual style

#niri

So yeah, I'm working on blur for niri. I'm doing "xray blur" first where the idea is that you only include background surfaces, so you pretty much never have to redo the blur—next to zero perf impact unless you have a video wallpaper or smth.

Turns out that it's quite tricky to do well, especially with our Overview. I'm like on my third refactor attempt now but I think I've got a good approach.

During this video there's no reblurring whatsoever, all just drawing cached static textures.

#niri

Added non-xray blur, based on @drakulix's Smithay/COSMIC implementation.

Keep in mind this blur work is still extremely WIP and with many issues (some visible on the video). It's also still not entirely clear to me how to best structure the code around it in niri. We'll see

#niri

Alright, getting somewhere! I think I've figured out a good code structure for the xray blur. It now correctly works even inside offscreens (opening animation, and when you drag a window targeting the tiling layout), and it should also work properly with the upcoming screen magnifier (that we have in pull requests).

Still not a single blur re-render in this entire video!

#niri

you know it's serious when you have to pull out a notebook to figure out the coordinate transforms

#niri

Today, got xray working on the closing window animations. The reason this needs special treatment is that when a window closes, niri renders a snapshot of its last visible contents to use for the animation. This happens outside the normal rendering path so I needed to thread through the xray background rendering logic as well as the correct window coordinates (since the xray background needs to know where the window is to draw the correct thing).

#niri

Today: implemented (a limited but useful subset of) both ext-background-effect and org-kde-kwin-blur protocols. Clients use these to request blur on their surfaces without having to configure anything in the compositor. These protocols also allow clients to blur only parts of their surfaces, for example here excluding client-side decoration bars and shadows.

Here are three terminals all with their org-kde-kwin-blur setting enabled.

#niri

I moved the niri repo from my personal GitHub to a new org: https://github.com/niri-wm/niri

I set up a redirect for GitHub Pages, so hopefully all old links keep working

The primary reason to move to an org is giving granular repo permissions, e.g. let Semper triage and manage issues (who's been doing a fantastic work helping with issues, thanks a ton!). This is unfortunately only possible in organizations and not in personal repos

We'll also add more related repos like awesome-niri to the org

#niri

Niri can block out windows from screencasts. This must work with all other niri features, including background blur. When the window itself is blocked out that's easy, but what if something in the background layer is blocked out?

Certainly turned out to be one of the trickiest pieces of logic to properly support this. Especially the window closing animation which renders a snapshot of the last visible window contents.

#niri

I've now implemented proper full region support for ext-background-effect and kde-blur protocols. Clients can use this to shape blur to their rounded corners for example.

Here's the Vicinae launcher [1] that added ext-background-effect support in their last release, with rounded corners and background blur on niri with no extra configuration.

[1]: https://github.com/vicinaehq/vicinae

#niri

niri has reached 20k stars on GitHub!   

pretty wild tbh

thanks everyone for support!  

#niri

Alright, I've finished most of the things that I wanted to finish, so I created a pull request for background blur in niri: https://github.com/niri-wm/niri/pull/3483

Please give it a good test and tell me if anything's broken!

#niri