ppl from our niri matrix playing around with the new compositor-side shadows! These screenshots are from @r4hulrosh4n and calops (no fedi)

#niri

Added shadow support for layer-shell surfaces!

Though unfortunately layer-shell has no way to signal the visual geometry, so this only looks right if the layer surface doesn't have its own margins.

https://github.com/YaLTeR/niri/wiki/Configuration:-Layer-Rules#shadow

#niri

Configuration: Layer Rules

A scrollable-tiling Wayland compositor. Contribute to YaLTeR/niri development by creating an account on GitHub.

GitHub

I'm adding tabs to niri. Instead of some separate mode, they're just changing how a column is displayed. This means all your hotkeys and everything works exactly the same with tabs. Which was a wonderful UX idea by @elkowar!

I've got a draft PR going with some design and UX questions, please feel free to try it and give feedback: https://github.com/YaLTeR/niri/pull/1085

#niri

Why would you even want tabs in niri? Occasionally it's quite useful. For example, when streaming programming, I increase the font size, so I can no longer fit editor + terminal on the screen at once. Scrolling back and forth gets annoying, and tabs feel just right for this.

We just hit 5000 stars! ๐ŸŽ‰

#niri

A ton of changes in the tabs PR over the past few days. Mainly various options (tabbed display by default, tab indicator position, etc.).

Just finished with a big one: you can now place the tab indicator within the column rather than "outside". This is needed for thicker tab bars, since otherwise they overlap adjacent windows.

https://github.com/YaLTeR/niri/pull/1085

#niri

Tabbed columns by YaLTeR ยท Pull Request #1085 ยท YaLTeR/niri

Tabbed display mode for columns. Implements #933 / #876. This is a WIP draft meant to gather feedback and figure out how exactly this should work. I know animations are broken, I'll deal with ...

GitHub

I merged tabbed columns into niri! Now you can play around with them using your nearest niri-git package. With working animations and all  

Noticed tabs can sometimes be useful for comparing windows without taking screenshots. Here for example I'm running the Adw demo from F41 vs. nightly Flathub, showing the slight color difference and apparently a 1 px layout shift.

#niri

Another cool suggestion by @elkowar: you can now match windows recorded by an active window screencast. For example, to highlight the casted window with a different color.

#niri

Configuration: Key Bindings

A scrollable-tiling Wayland compositor. Contribute to YaLTeR/niri development by creating an account on GitHub.

GitHub

Today in *very long* overdue features (looks like I opened the issue even before v0.1.0): moving the mouse against a monitor edge now scrolls the view during drag-and-drop.

(before this change, you had to use the keyboard for this, and yes it was very awkward)

#niri

Another neat new thing: a bind to expand column to available width. Basically, "expand to fill empty space".

But, a bit smarter: with scrollable tiling we can have windows partially off-screen. This bind ignores such windows, making it easy to position things to exactly fill the screen, even in the middle of a scrolling layout.

#niri

Today I'm releasing niri v25.02 with tabs, shadows, DnD view scrolling, and a ton of other improvements! Read the release notes at https://github.com/YaLTeR/niri/releases/tag/v25.02 and @ your distro to update the package.  

[[honestly wtf how did so much stuff happen, it's been barely over a month]]

#niri #smithay #wayland #rust

This is not on main yet, but I've heavily reworked how offscreening works in niri.

Offscreening is when you render a group of elements to a separate texture, then draw that texture to the final render. In niri it's used for window opening and resize animations, and now also for full-tile opacity changes.

Before, it was very simple: every frame create a new texture and render it from scratch. The new code caches textures and does full damage tracking both "inside" and "outside" the offscreen.

In practice this means much less texture re-creations and much less redrawing.

The main reason to do this was to unlock using offscreens for more persistent visuals. E.g. it's fine to do some extra rendering for a 150 ms animation, but it's not fine to do it for something that can last seconds or minutes.

In particular, I can finally make windows semitransparent while dragging them in the tiling layout! Which needs an offscreen since it's a stack of border + window + subsurfaces.

#niri

Still testing this one: a window rule to set the xdg-toplevel Tiled state.

By default niri matches it to prefer-no-csd, because the Tiled state currently happens to be the best way to ask always-CSD windows to square their corners.

With this tiled-state window rule you can override it, for example to get title bars (for easy mouse-only gestures) together with square corners (if you're going for a square style with borders, like mine here). You can also e.g. limit it to tiled windows.

#niri

And another thing for today: finally made it so niri waits a bit for the lock screen to paint before locking the session. This fixes the "red flash" issue.

Please test this since it's security sensitive. I already caught one mistake before pushing where killing a lock screen, then spawning a new one, would briefly flash the session contents.

(Note that some lockers fade in from transparency, so you'll still briefly see red, that's just the niri locked session background.)

#niri

Since adding tabbed columns, just about everyone is asking for a way to open a new window directly in the focused tabbed column. This is rather complicated, but yesterday I came up with a 1 line change that should cover some workflows (covers how I use tabs at least).

I have logic that restores the view position when you open and close a window right away. Now I enabled it for consume-left, which means that you can open a new window, consume left (into a tab), and the view will go back.

#niri

Today I implemented a new niri screencasting feature: the dynamic cast target.

It shows up as a special "window" in the portal dialog. Once you select it, you can change what it casts with niri binds! Switch between windows, monitors, and in the future maybe workspaces and other stuff. Works with OBS, browsers, anything else.

I also wrote a wiki page with all our screencasting-related features: https://github.com/YaLTeR/niri/wiki/Screencasting

Thanks @elkowar for coming up with the dynamic cast idea!

#niri

Screencasting

A scrollable-tiling Wayland compositor. Contribute to YaLTeR/niri development by creating an account on GitHub.

GitHub

Had to show slides a few times for uni lately, which motivated me to add this next feature.

Windowed fullscreen, also known in other WMs as fake or detached fullscreen, makes the window think that it went fullscreen, while in reality keeping it as a normal window. Useful in combination with apps like Google Slides to hide the browser UI without taking up the whole screen, especially on ultrawide monitors.

Wiki section: https://github.com/YaLTeR/niri/wiki/Screencasting#windowed-fakedetached-fullscreen

#niri

Screencasting

A scrollable-tiling Wayland compositor. Contribute to YaLTeR/niri development by creating an account on GitHub.

GitHub

This one seems simple, but actually turned out quite tricky to implement.

I wrote niri code under the assumption that the fullscreen state does not apply immediately: we send a configure to the window, then only at a later point it commits in response. Windowed fullscreen breaks this because in some cases it can apply instantly (going from real to windowed fullscreen needs no state change from the window).

#niri

After trying a few approaches, I ended up doing it "properly" by associating the (entirely compositor-side) windowed fullscreen state to window configures and commits. This lets niri correctly track if a given fullscreen window commit was real fullscreen (so e.g. we need to draw a black backdrop), or if it was windowed fullscreen.

This even works across a chain of toggling windowed fullscreen, then the window slowly acking and committing them, and I have a test to verify that.

#niri

New niri users frequently come from other tiling WMs with static workspace systems. For them, dynamic workspaces is an unusual system, and it can be unclear how to use dynamic workspaces effectively. (Especially until we get an Overview type thing.)

I figured I'd write a wiki page describing niri's workspaces in more detail: https://github.com/YaLTeR/niri/wiki/Workspaces I also included an example of how I personally use workspaces on niri.

Hopefully this makes it easier to understand what's going on!

#niri

Workspaces

A scrollable-tiling Wayland compositor. Contribute to YaLTeR/niri development by creating an account on GitHub.

GitHub

slowly going through the piled up PRs (how's your weekend going?), today merged the pick-color IPC from nnyyxxxx. comes with Portal support of course

#niri

A secret niri v25.02 feature! Make your floating windows FLOAT by putting this in your config:

window-rule {
match is-floating=true
baba-is-float true
}

Works in the nix flake too  

#niri #wayland

started working on an Overview for niri. very wip, lots to do, got some basic rendering and dragging working though

#niri

today's progress: wheel scrolling up and down, right click to scroll left and right, click on workspace to focus, some keyboard fixes

this is all mouse-only on the video. only currently using a 3rd-party tool for the hot corner (waycorner), i'll integrate that later

#niri

i have this old ASUS Eee PC collecting dust, decided to try if niri will run on it. well, it actually runs! a few shaders failed compiling (ran into ALU instruction limits), but otherwise seems to work

#niri

today's overview progress: some rendering and input fixes, plus implemented built-in hot corner, and workspace switch on drag-and-drop hold. which means that now you can perform an entire drag-and-drop to a different workspace mouse-only!

#niri

spent many hours today trying to make the combined exit overview + switch workspace animation monotonic. This is hard because zoom and vertical movement are separate axes, and you can e.g. "catch" one of them with a touchpad gesture, while the other must continue animating (so you can't easily convert this into rect interpolation).

Ended up working out a correction formula for the workspace Y positions when both axes have matching animations. Appears to behave so far from my testing

#niri

today I opened a draft PR for the Overview, and request everyone to test it and report issues: https://github.com/YaLTeR/niri/pull/1440

also, today's new overview feature: drag-and-drop into a new workspace between/above/below!

#niri

Overview by YaLTeR ยท Pull Request #1440 ยท YaLTeR/niri

Implements #850. Related: #849. This is an overview. It zooms out your workspaces and lets you move your windows around. niri-wip-overview-4.mp4 Open it with a ...

GitHub

POV: GoPro mounted on the xwayland-satellite

#niri

Today: added touch support to the Overview. Somehow, the entire thing just worked first try.

#niri

After some more fixes, and a long rebasing session, I merged the Overview! Please give it more testing using your nearest niri-git package.

https://github.com/YaLTeR/niri/wiki/Overview

#niri

Overview

A scrollable-tiling Wayland compositor. Contribute to YaLTeR/niri development by creating an account on GitHub.

GitHub

The Eee PC rocking the Overview

#niri

Ppl naturally want to put something in the Overview backdrop, like a blurred version of the wallpaper (see how popular Blur My Shell is). Orthogonally, some ppl want the wallpaper to be static, rather than move with workspaces (it can be distracting).

I'm not prepared to dive head-first into image rendering and blur shaders yet, so I made it possible to put a layer surface into the backdrop. This enables both of those cases, likely even more cool things!

https://github.com/YaLTeR/niri/wiki/Overview#backdrop-customization

#niri

Overview

A scrollable-tiling Wayland compositor. Contribute to YaLTeR/niri development by creating an account on GitHub.

GitHub

Today, screenshot UI updates! Implemented tablet and touchscreen input for area selection (at long last). And, added a small clickable capture button, so screenshots can now be confirmed tablet-, touch-, or mouse-only!

#niri

After long 3 months of work, I'm glad to release niri v25.05 with the Overview, screenshot UI tablet and touch support, dynamic screencast target and windowed fullscreen, IPC pick-window and pick-color, window urgency, and lots of other things!   

Release notes prepared for your reading pleasure as always: https://github.com/YaLTeR/niri/releases/tag/v25.05

#niri #smithay #rust #wayland

Release v25.05 ยท YaLTeR/niri

Niri is a scrollable-tiling Wayland compositor. Windows are arranged in columns on an infinite strip going to the right. Opening a new window never causes existing windows to resize. Here are the i...

GitHub

Tagged a niri v25.05.1 hotfix, fixing kitty quick access terminal, numlock, and some jank with hidden cursor.

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

#niri

Release v25.05.1 ยท YaLTeR/niri

This is a hotfix release for niri v25.05. Fixed handling of layer surfaces unmapped through a null buffer commit: they will now receive an initial configure as necessary (thanks @alex-huff). This ...

GitHub

Alright after some much needed rest, I set out to deal with the thing everyone has to bump into when setting up niri: some way to use Xwayland. I am still very much *not* planning to integrate Xwayland directly, but with this PR (and an accompanying xwayland-satellite PR), niri will create the X11 sockets and autostart xwl-s on demand, all out of the box with zero configuration. So, it'll work just like other compositors, but with xwl-s instead of direct Xwayland.

https://github.com/YaLTeR/niri/pull/1728

#niri

Automatic xwayland-satellite integration by YaLTeR ยท Pull Request #1728 ยท YaLTeR/niri

When a recent enough (with this PR) xwayland-satellite is detected, niri will create the X11 sockets and set DISPLAY, then automatically spawn xwayland-satellite when an X11 client tries to connect...

GitHub

8k stars! ๐ŸŽ‰

#niri

In niri v25.05, the screenshot UI learned to respond to some keyboard window movement bindings by moving the screenshot selection. Now it supports several more movement commands, including moving across monitors. It works similarly to a floating window: the selection origin is preserved relatively, and the size is adjusted by the monitor scale difference. Under the right conditions, it'll match a floating window exactly.

Also, holding Space will now let you move the selection origin!

#niri

...and now moving also works with on a touchscreen with a second touch :) Got this idea from how in osu! you can drag with one finger and press with second/third to "click".

#niri

apparently niri is on the GH trending page today: https://github.com/trending Amidst a sea of LLM repos ๐Ÿ™ƒ

#niri

Today I implemented most of the ext-workspace protocol [1] in niri. It lets desktop components (i.e. bars) show workspaces and do some basic operations on them.

The two bars with ext-workspace that I know of are sfwbar and xfce4-panel. Unfortunately, I seem to have surfaced several problems in their implementations. I opened issues in sfwbar; would be great if someone took a look from Xfce. Also if there are other clients I missed?

https://github.com/YaLTeR/niri/pull/1800

[1]: https://wayland.app/protocols/ext-workspace-v1

#niri

Implement ext-workspace by YaLTeR ยท Pull Request #1800 ยท YaLTeR/niri

Implements #135. TODO: ext_workspace_manager_v1::commit() request (currently changes are applied right away). Also, apparently the two existing clients (sfwbar and xfce4-panel) are quite broken? Wi...

GitHub

Everyone who dislikes GitHub Wiki: I finally made a write-down of my requirements/wishes for a replacement. Please feel free to chime in with suggestions: https://github.com/YaLTeR/niri/discussions/1830

#niri

GitHub Wiki replacement ideas ยท YaLTeR niri ยท Discussion #1830

The GitHub Wiki is very convenient for me as the developer (it's right there, it's simple and it works), but it has some glaring issues, most notably the lack of a good search. (You can in fact sea...

GitHub

Update on ext-workspace:
- sfwbar fixed all outstanding issues!
- the waybar ext-workspace PR also fixed all issues!
- quickshell impl is on the way

#niri

Out of curiosity, I tried running Orca on niri, and apparently it sort-of works for some apps (I expected nothing to work at all; idk anything about screen readers). However, compared to GNOME Shell, there's quite a few missing or broken things. I documented what I found here: https://github.com/YaLTeR/niri/issues/1904

Is there some "Integrating Orca to Wayland desktops" docs? Like, what the compositor needs to do, who handles the hotkeys and how, etc.

(not actively working on this, just curious)

#niri #a11y

Investigate screen reader support ยท Issue #1904 ยท YaLTeR/niri

Disclaimer: I have very little idea about how any of this works. I'm testing on Fedora 42 Silverblue. As of now, apparently, just running orca is enough to get in-app screen reading and, for some t...

GitHub

Should've done this a while ago, but I finally wrote contributing guidelines for niri:

https://github.com/YaLTeR/niri/blob/main/CONTRIBUTING.md

With many new users, the stream of issues, discussions and pull requests is quite overwhelming. ๐Ÿ˜… You can help! And the contributing guidelines outline the various ways how.

I would especially appreciate help reviewing PRs, though I understand it's the more complex task out of these.

Big thanks to people already answering questions and helping others! 

#niri

Today I implemented fetching keyboard layout options from org.freedesktop.locale1, used by things like distro installers to configure the layout:

https://github.com/YaLTeR/niri/pull/2052

I guess this is the closest thing to global cross-desktop keyboard layout configuration, so it should also help environments like LXQt integrating niri.

Also recently merged: niri now sets a logind session locked hint, useful for e.g. idle tools that put the PC to sleep, but only once the lockscreen is fully up.

#niri

Implement fetching xkb options from org.freedesktop.locale1 by YaLTeR ยท Pull Request #2052 ยท YaLTeR/niri

Implements #1588 cc @Conan-Kudo

GitHub

Gathering thoughts on reconciling communities between Matrix and Discord: https://github.com/YaLTeR/niri/discussions/2069

This is a problem I expect we'll face reasonably soon, so if you have some ideas please write in the discussion!

#niri

Discord server (and its coexistence with Matrix) ยท YaLTeR niri ยท Discussion #2069

Two weeks or so ago, @Purian23 has created a Discord server for niri: https://discord.gg/vT8Sfjy7sx A few days ago I joined too, which I suppose makes it semi-official. If it keeps going well, I'll...

GitHub

About finished implementing org.fd.a11y.KeyboardMonitor in niri, necessary for correct screen reader function:

https://github.com/YaLTeR/niri/pull/2060

I tested it with Orca more or less, seems to work, but I'm very new to screen reader workings, so it's possible I've missed something.

This makes Orca announce keys everywhere in niri, and makes grabs work (both modifier with double-press passthrough and keystrokes). Making Orca actually say niri dialogs will be a separate effort.

#niri #a11y

We made it to 10k stars on GitHub!!!!    

#niri

Finally finished making niri screencasts asynchronously wait for rendering completion before handing the buffer over to PipeWire. This fixes screencast flickering problems on NVIDIA setups.

https://github.com/YaLTeR/niri/pull/2175

This is not PW explicit sync; I can now finish that too (OBS and PW released their fixes), but it'll act more as an optimization on top of the current code (since only OBS can use it for now, and not on its Flathub build (PW is too old there)).

#niri

Asynchronously wait for frame completion in PipeWire by YaLTeR ยท Pull Request #2175 ยท YaLTeR/niri

Along with a bunch of refactors in preparation for PW explicit sync. In theory, fixes #1432 (the issue therein). Needs testing from NVIDIA users who experience the screencast flickering issue.

GitHub

Quite comprehensive desktop shell for niri released today: https://github.com/bbedward/DankMaterialShell

Based on QuickShell; made by the same people who started the niri Discord server.

Checking it out now, looks very cool! Though not without a few rough edges to iron out of course

#niri #quickshell

today niri turns 2!

#niri

@YaLTeR Congratulations, keep up the great work! :)

@YaLTeR congrats

Its so good for being only 2 y.o.

@YaLTeR
This is awesome! I'm always a sucker for shiny stuff but unfortunately this will rarely see a #opensuse repository.
@mueggl @YaLTeR Eh? Niri is in Tumbleweed, has been for quite a while?
@sfalken @YaLTeR
No, I meant darkmaterialshell. Been running niri for a long time.
...and stuff like #gbar #ashell #kickoff #zenway #walker #findex #dynisland #unirun #wayedges #sherlock #softosd
@YaLTeR ooh looks like I found something to package up tonight! ๐Ÿคญ
@YaLTeR I'm not super vibing with the styling but it looks really impressive
@BrodieOnLinux yeah, hopefully these kinds of projects reduce the gap for ppl to try niri
@YaLTeR Huh, didn't know QuickShell supported Niri.
@Flaky why wouldn't it? It's just layer-shell
@YaLTeR The website made it seem like it was more for Hyprland to me lol. Might give this a shot.
@YaLTeR ooh boy here I go ricing again
@YaLTeR
Well deserved! ๐Ÿ‘
@YaLTeR I didn't realize this was a continuous thread from the start of the project, I respect the dedication
@BrodieOnLinux I think it's more fun this way
@YaLTeR @BrodieOnLinux i love that it takes a good 20 seconds to open any post from this thread from my instance :P

@YaLTeR @BrodieOnLinux huge megathreads do often cause issues with some clients though (like in tuba where clicking on one just crashes the entire app)โ€ฆ

mastodon added featured hashtags for exactly this purpose, maybe it would be worth using those instead?

@tromino @BrodieOnLinux

> like in tuba where clicking on one just crashes the entire app

@bugaevc ? :)

@BrodieOnLinux @YaLTeR And it's so great to see an alternative window manager thrive. Love Niri!
@YaLTeR I know Discord and stuff sounds great, but wouldn't something like Zulip be much better for an open source project?

It's much less of a walled garden and many other projects (for example
https://rust-lang.zulipchat.com/) benefit from the openness and forum-chat hybrid model
Public view of rust-lang | Zulip team chat

Browse the publicly accessible channels in rust-lang without logging in.

Zulip
@natty well, we're not picking a platform. We're faced with the fact that a Discord now exists and will inevitably get more users, and so we need to figure out how to best handle the existence of two separate active communication platforms
@YaLTeR Yeah I got a little ahead of myself, our reasoning was that bridging the two could quickly outgrow a Matrix especially in terms of moderation and community management
@YaLTeR fwiw the only things I have heard about matrix recently were very much negative and I hate siding with discord on this argument for reasons you already outlined.

Also please make sure any documentation is available outside of either platform, ideally where archival and search engines are possible. I have literally stopped using software because I can't keep joining discord servers for every tiny little piece of software that makes my desktop work and only getting documentation/support on discord made the software impossible to use without.
@mitsunee all docs are in the niri repo dw
@YaLTeR Crazy how much you've done ever since!!
@YaLTeR
**mdBook** is very usable
@apsnyog @YaLTeR mdbook is terrible for accessibility. For example, icons are rendered via web fonts, so when web fonts are disabled, all icons are impossible to recognise.
@whynothugo @YaLTeR
Is it one example only?

@apsnyog @YaLTeR "Navigation icons are broken and are not accompanied by any textual labels" is enough to make it entirely unusable.

I don't recall any other issues, it's so utterly unusable that I don't (can't) consume sites rendered with it.

@YaLTeR sounds like material for mkdocs ticks all boxes. We use it for everything and are extremely satisfied with it.
@ju someone suggested it in the discussion, but it doesn't seem like it can render the GitHub admonition syntax?

@YaLTeR yeah I saw that afterwards.

If that is a priority, then I guess you'd be better served with alternatives.

I also have good experiences with vuepress, so I assume it's successor vitepress is good as well.

@ju to update on this after one of our users have been tinkering with mkdocs-material:
- GitHub admonitions seem to be supported by a "github-callouts" feature from the "markdown-callouts" extension
- they got KDL highlighting working in pygments and I think they intend to try upstreaming it
- they got most of the other stuff that I wanted working too

So perhaps mkdocs-material will indeed be a good choice

@YaLTeR that's great!

I basically have no complaints about this.

Interested to see how it will work for you.

Alternatively, I also like this one https://starlight.astro.build/

Starlight ๐ŸŒŸ Build documentation sites with Astro

Starlight helps you build beautiful, high-performance documentation websites with Astro.

Starlight
@YaLTeR i use gBar which to my knowledge also implements ext-workspace
@YaLTeR cosmic-panel? with the workspace-addon?
@drakulix hmm, I installed cosmic-{panel,applets,workspaces} from Fedora, and on a build without ext-workspace cosmic-panel runs fine, but on a build with ext-workspace it exits silently with code 101. I tried gdb with follow-fork-mode child but couldn't really make sense of it, a bunch of broken pipes concluding in a sigabrt in unrelated modules
@YaLTeR oh interesting. I am not sure we had a compositor to test on before with *just* an ext-workspaces implementation, but not cosmic-workspaces. I'll look into it :)
@YaLTeR Looks convenient! Although I would never discover this gesture if I didn't know it exists ๐Ÿค”
@luley yea well it's not a super important gesture, and i don't have a good idea where to document it other than the wiki (especially considering that most people aren't on touchscreens)
@YaLTeR yes! I was about to suggest the <Space> binding
ร—

8k stars! ๐ŸŽ‰

#niri

In niri v25.05, the screenshot UI learned to respond to some keyboard window movement bindings by moving the screenshot selection. Now it supports several more movement commands, including moving across monitors. It works similarly to a floating window: the selection origin is preserved relatively, and the size is adjusted by the monitor scale difference. Under the right conditions, it'll match a floating window exactly.

Also, holding Space will now let you move the selection origin!

#niri

...and now moving also works with on a touchscreen with a second touch :) Got this idea from how in osu! you can drag with one finger and press with second/third to "click".

#niri

apparently niri is on the GH trending page today: https://github.com/trending Amidst a sea of LLM repos ๐Ÿ™ƒ

#niri

Today I implemented most of the ext-workspace protocol [1] in niri. It lets desktop components (i.e. bars) show workspaces and do some basic operations on them.

The two bars with ext-workspace that I know of are sfwbar and xfce4-panel. Unfortunately, I seem to have surfaced several problems in their implementations. I opened issues in sfwbar; would be great if someone took a look from Xfce. Also if there are other clients I missed?

https://github.com/YaLTeR/niri/pull/1800

[1]: https://wayland.app/protocols/ext-workspace-v1

#niri

Implement ext-workspace by YaLTeR ยท Pull Request #1800 ยท YaLTeR/niri

Implements #135. TODO: ext_workspace_manager_v1::commit() request (currently changes are applied right away). Also, apparently the two existing clients (sfwbar and xfce4-panel) are quite broken? Wi...

GitHub

Everyone who dislikes GitHub Wiki: I finally made a write-down of my requirements/wishes for a replacement. Please feel free to chime in with suggestions: https://github.com/YaLTeR/niri/discussions/1830

#niri

GitHub Wiki replacement ideas ยท YaLTeR niri ยท Discussion #1830

The GitHub Wiki is very convenient for me as the developer (it's right there, it's simple and it works), but it has some glaring issues, most notably the lack of a good search. (You can in fact sea...

GitHub

Update on ext-workspace:
- sfwbar fixed all outstanding issues!
- the waybar ext-workspace PR also fixed all issues!
- quickshell impl is on the way

#niri

Out of curiosity, I tried running Orca on niri, and apparently it sort-of works for some apps (I expected nothing to work at all; idk anything about screen readers). However, compared to GNOME Shell, there's quite a few missing or broken things. I documented what I found here: https://github.com/YaLTeR/niri/issues/1904

Is there some "Integrating Orca to Wayland desktops" docs? Like, what the compositor needs to do, who handles the hotkeys and how, etc.

(not actively working on this, just curious)

#niri #a11y

Investigate screen reader support ยท Issue #1904 ยท YaLTeR/niri

Disclaimer: I have very little idea about how any of this works. I'm testing on Fedora 42 Silverblue. As of now, apparently, just running orca is enough to get in-app screen reading and, for some t...

GitHub

Should've done this a while ago, but I finally wrote contributing guidelines for niri:

https://github.com/YaLTeR/niri/blob/main/CONTRIBUTING.md

With many new users, the stream of issues, discussions and pull requests is quite overwhelming. ๐Ÿ˜… You can help! And the contributing guidelines outline the various ways how.

I would especially appreciate help reviewing PRs, though I understand it's the more complex task out of these.

Big thanks to people already answering questions and helping others! 

#niri

Today I implemented fetching keyboard layout options from org.freedesktop.locale1, used by things like distro installers to configure the layout:

https://github.com/YaLTeR/niri/pull/2052

I guess this is the closest thing to global cross-desktop keyboard layout configuration, so it should also help environments like LXQt integrating niri.

Also recently merged: niri now sets a logind session locked hint, useful for e.g. idle tools that put the PC to sleep, but only once the lockscreen is fully up.

#niri

Implement fetching xkb options from org.freedesktop.locale1 by YaLTeR ยท Pull Request #2052 ยท YaLTeR/niri

Implements #1588 cc @Conan-Kudo

GitHub

Gathering thoughts on reconciling communities between Matrix and Discord: https://github.com/YaLTeR/niri/discussions/2069

This is a problem I expect we'll face reasonably soon, so if you have some ideas please write in the discussion!

#niri

Discord server (and its coexistence with Matrix) ยท YaLTeR niri ยท Discussion #2069

Two weeks or so ago, @Purian23 has created a Discord server for niri: https://discord.gg/vT8Sfjy7sx A few days ago I joined too, which I suppose makes it semi-official. If it keeps going well, I'll...

GitHub

About finished implementing org.fd.a11y.KeyboardMonitor in niri, necessary for correct screen reader function:

https://github.com/YaLTeR/niri/pull/2060

I tested it with Orca more or less, seems to work, but I'm very new to screen reader workings, so it's possible I've missed something.

This makes Orca announce keys everywhere in niri, and makes grabs work (both modifier with double-press passthrough and keystrokes). Making Orca actually say niri dialogs will be a separate effort.

#niri #a11y

We made it to 10k stars on GitHub!!!!    

#niri

Finally finished making niri screencasts asynchronously wait for rendering completion before handing the buffer over to PipeWire. This fixes screencast flickering problems on NVIDIA setups.

https://github.com/YaLTeR/niri/pull/2175

This is not PW explicit sync; I can now finish that too (OBS and PW released their fixes), but it'll act more as an optimization on top of the current code (since only OBS can use it for now, and not on its Flathub build (PW is too old there)).

#niri

Asynchronously wait for frame completion in PipeWire by YaLTeR ยท Pull Request #2175 ยท YaLTeR/niri

Along with a bunch of refactors in preparation for PW explicit sync. In theory, fixes #1432 (the issue therein). Needs testing from NVIDIA users who experience the screencast flickering issue.

GitHub

Quite comprehensive desktop shell for niri released today: https://github.com/bbedward/DankMaterialShell

Based on QuickShell; made by the same people who started the niri Discord server.

Checking it out now, looks very cool! Though not without a few rough edges to iron out of course

#niri #quickshell

today niri turns 2!

#niri

@YaLTeR Congratulations, keep up the great work! :)
@YaLTeR
This is awesome! I'm always a sucker for shiny stuff but unfortunately this will rarely see a #opensuse repository.
@mueggl @YaLTeR Eh? Niri is in Tumbleweed, has been for quite a while?
@sfalken @YaLTeR
No, I meant darkmaterialshell. Been running niri for a long time.
...and stuff like #gbar #ashell #kickoff #zenway #walker #findex #dynisland #unirun #wayedges #sherlock #softosd
@YaLTeR ooh looks like I found something to package up tonight! ๐Ÿคญ
@YaLTeR I'm not super vibing with the styling but it looks really impressive
@BrodieOnLinux yeah, hopefully these kinds of projects reduce the gap for ppl to try niri
@YaLTeR Huh, didn't know QuickShell supported Niri.
@Flaky why wouldn't it? It's just layer-shell
@YaLTeR The website made it seem like it was more for Hyprland to me lol. Might give this a shot.
@YaLTeR
Well deserved! ๐Ÿ‘
@YaLTeR I didn't realize this was a continuous thread from the start of the project, I respect the dedication
@BrodieOnLinux I think it's more fun this way
@YaLTeR @BrodieOnLinux i love that it takes a good 20 seconds to open any post from this thread from my instance :P

@YaLTeR @BrodieOnLinux huge megathreads do often cause issues with some clients though (like in tuba where clicking on one just crashes the entire app)โ€ฆ

mastodon added featured hashtags for exactly this purpose, maybe it would be worth using those instead?

@tromino @BrodieOnLinux

> like in tuba where clicking on one just crashes the entire app

@bugaevc ? :)

@BrodieOnLinux @YaLTeR And it's so great to see an alternative window manager thrive. Love Niri!
@YaLTeR I know Discord and stuff sounds great, but wouldn't something like Zulip be much better for an open source project?

It's much less of a walled garden and many other projects (for example
https://rust-lang.zulipchat.com/) benefit from the openness and forum-chat hybrid model
Public view of rust-lang | Zulip team chat

Browse the publicly accessible channels in rust-lang without logging in.

Zulip
@natty well, we're not picking a platform. We're faced with the fact that a Discord now exists and will inevitably get more users, and so we need to figure out how to best handle the existence of two separate active communication platforms
@YaLTeR Yeah I got a little ahead of myself, our reasoning was that bridging the two could quickly outgrow a Matrix especially in terms of moderation and community management
@YaLTeR Crazy how much you've done ever since!!
@YaLTeR
**mdBook** is very usable
@apsnyog @YaLTeR mdbook is terrible for accessibility. For example, icons are rendered via web fonts, so when web fonts are disabled, all icons are impossible to recognise.
@whynothugo @YaLTeR
Is it one example only?

@apsnyog @YaLTeR "Navigation icons are broken and are not accompanied by any textual labels" is enough to make it entirely unusable.

I don't recall any other issues, it's so utterly unusable that I don't (can't) consume sites rendered with it.

@YaLTeR sounds like material for mkdocs ticks all boxes. We use it for everything and are extremely satisfied with it.
@ju someone suggested it in the discussion, but it doesn't seem like it can render the GitHub admonition syntax?

@YaLTeR yeah I saw that afterwards.

If that is a priority, then I guess you'd be better served with alternatives.

I also have good experiences with vuepress, so I assume it's successor vitepress is good as well.

@ju to update on this after one of our users have been tinkering with mkdocs-material:
- GitHub admonitions seem to be supported by a "github-callouts" feature from the "markdown-callouts" extension
- they got KDL highlighting working in pygments and I think they intend to try upstreaming it
- they got most of the other stuff that I wanted working too

So perhaps mkdocs-material will indeed be a good choice

@YaLTeR that's great!

I basically have no complaints about this.

Interested to see how it will work for you.

Alternatively, I also like this one https://starlight.astro.build/

Starlight ๐ŸŒŸ Build documentation sites with Astro

Starlight helps you build beautiful, high-performance documentation websites with Astro.

Starlight
@YaLTeR i use gBar which to my knowledge also implements ext-workspace
@YaLTeR cosmic-panel? with the workspace-addon?
@drakulix hmm, I installed cosmic-{panel,applets,workspaces} from Fedora, and on a build without ext-workspace cosmic-panel runs fine, but on a build with ext-workspace it exits silently with code 101. I tried gdb with follow-fork-mode child but couldn't really make sense of it, a bunch of broken pipes concluding in a sigabrt in unrelated modules
@YaLTeR oh interesting. I am not sure we had a compositor to test on before with *just* an ext-workspaces implementation, but not cosmic-workspaces. I'll look into it :)
@YaLTeR Looks convenient! Although I would never discover this gesture if I didn't know it exists ๐Ÿค”
@luley yea well it's not a super important gesture, and i don't have a good idea where to document it other than the wiki (especially considering that most people aren't on touchscreens)
@YaLTeR yes! I was about to suggest the <Space> binding
@YaLTeR Well deserved! :)

@YaLTeR
Thank you for making niri. It clicks so good for certain workflows. I'm an happy user.

stars will keep on rising just as this long thread is rising. ๐Ÿ˜

@YaLTeR
Plus alot of invisible stars from people who do not use github.
Feel hugged ๐Ÿ™‚

#niri

@YaLTeR
Congrats and thanks!
niri replaced hyprland on 3 machines.
I kept one for the feel. ;-)