niri-wm/niri

Actually for me it's different. I've been using Tmux and later Zellij for many years, while I was on Ubuntu's Unity, then Gnome, KDE, i3 and lastly sway. Until I switched to niri ( https://github.com/niri-wm/niri ) ... since then I haven't used tmux at all. Very weird, come to think of.

The only remaining feature I would like is focus-follows-mouse but only for outputs, so that if I've moved my mouse over onto a second monitor, the focus moves to that output. There are a few discussions around this, so I'm hopeful to see it implemented at some point: - https://github.com/niri-wm/niri/discussions/1318 - https://github.com/niri-wm/niri/discussions/378 - https://github.com/niri-wm/niri/discussions/491

I switched to Niri ( https://github.com/niri-wm/niri ) about six months ago and I find it does wonders for focus. Set the default window width to 1/4 or 1/3 of the screen width (depending on the screen size) and it's easy to keep just the right context visible.

Niri¹ is awesome. It took quite a bit of customization when I originally installed it, however, quite a few things have improved since then. I believe that niri's out-of-the-box experience is reasonably good with the latest version. With the addition noctalia², it really feels like a complete desktop and offers the essential functionality that I'd expect from gnome or kde. 1. https://github.com/YaLTeR/niri 2. https://docs.noctalia.dev/getting-started/installation/

I'm not a Niri stan by any means - I only switched to it the other week, and was using sway/i3 before then - but I suspect that most alternatives have answers to these, too. > Especially how it handles workspaces on multiple monitors. By default, each monitor has one workspace. Not one workspace for ALL monitors. I'm pretty sure this is the case for most tiling WMs; it's definitely the case for Niri ( https://github.com/YaLTeR/niri/wiki/Workspaces ), and I'm pretty sure it's the case for sway. > It also has hot reloading of the config, which is also nice. Niri will reload your config on save; Sway requires a keybind, but no restart. > Sure, Niri's config is approachable, but is it hacka…

I haven't tried it myself but niri might do what you want using Wayland https://github.com/niri-wm/niri

Maybe you'd like Niri? https://github.com/niri-wm/niri

Fair enough. "Overview" [0] presumably solves this, though. [0] https://github.com/YaLTeR/niri/wiki/Overview

… a big display, and splitting a display (moments before the multi-pointer ticket was filed in Niri), https://github.com/niri-wm/niri/discussions/1285 https://github.com/niri-wm/niri/discussions/3160 There's been all kinds of rough incredibly hard things going on with Niri just trying to figure out how to handle some of the more interesting copy-paste scenarios, and with really weird sequencing issues across basically ephemeral inputs, that have really plagued the project and made life incredibly bad for downstream apps. This is just my opinion, man, but I think the lack of ambition about these ridiculous over the top features eventually starts hampering what turns out to be relatively prosa…

Looking at a video demo of Niri for an example: https://github.com/YaLTeR/niri Conceptually, it's like an infinite 2D canvas windows, divided into strips (strip is a workspace), and you then scroll through an infinite ribbon of windows in each strip. Seems interesting, but also slower and less flexible than traditional tiling WMs (least of all because of the slow scrolling animations, but also because it seems to prefer scrolling instead of jumping-towards). Like most of the 'tiling with gaps' patches I see, these feel like trying to look fancy without necessarily delivering big value. I'd be interested to hear why people want a scrolling WM. Is it merely more visually pleasing?