Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Niri – A scrollable-tiling Wayland compositor

github.com

Post reply on HN
Print view View original

51–60 of 234 posts

Re: Niri – A scrollable-tiling Wayland compositor

#51

Post by argiopetech »

ducktective wrote: post #46
benoliver999 wrote: post #42

Earlier quoted context omitted.

Yes same here but with i3, I ran it for over 10 years but niri was just an instant 'aha' moment for me. I will say, recent builds have a 'mini map' sort of zoom-out feature that I quite like - my one critique of niri was that I would sometimes get 'lost'.

One of the advantages of tilling wm are that every window that is run, is visible too. Nothing invisible exists. But in this "endless horizontal tilling" scheme, the above principle would no longer hold, right?

Newly started applications receive focus, so they're visible by default. They are inserted right of the current view, so recovering the previous active pane is consistent ("left pane" keybinding, or the appropriate gesture).

Things on other desktops are invisible in every WM.

The only difference with niri is the possibility for things to be left or right of the current window. Overview helps with that, but I know what I expect to be on a specific desktop (it's related to the topic) and seldom need it.

Re: Niri – A scrollable-tiling Wayland compositor

#52

Post by nickjj »

One thing that was holding me back from trying Niri is its configuration was limited to 1 file with no way to override or include additional configs which is quite important IMO for having 1 main config that you slightly change on different devices if you want to make your dotfiles public. For example you can have gitignored "local" files on each device to handle overrides.

Just the other day the author merged 2 PRs to handle both use cases https://github.com/YaLTeR/niri/pull/2482.

It's not in a release yet but hopefully soon.

Re: Niri – A scrollable-tiling Wayland compositor

#53

Post by argiopetech »

atlintots wrote: post #47
ducktective wrote: post #46

Earlier quoted context omitted.

One of the advantages of tilling wm are that every window that is run, is visible too. Nothing invisible exists. But in this "endless horizontal tilling" scheme, the above principle would no longer hold, right?

That's true, you do end up with some windows hidden or partially visible. Niri is still tiling, though, so with proper management you can avoid making too much use of the infinite strip (though that would defeat the purpose of niri).

This seems like a good place to note the "center window" keybinding for windows that don't fit well in the screen (e.g., 2/3 wide pane next to 2/3 wide pane, or 1/3 pane on the right end of the stack next to a full-screen pane).

Vastly preferable to having to look at the edge of the screen.

Re: Niri – A scrollable-tiling Wayland compositor

#55

Post by exasperaited »

baq wrote: post #6

I'm basically fullscreen with everything all the time on macos, but not in the super-duper-fullscreen mode so cmd-tab/cmd-` works predictably. I want this on macos. I know I can't have it on macos. I also can't switch to Linux since macos is mandated by my employer. Nothing really to take out of it except that I feel like I'm not alone feeling stuck, knowing there are better workflows and not being able to do anythin…

I love the full-fullscreen mode for things like VSCode and FreeCAD on my 13" MBP. Never have a real issue with alt-tab though I must say I do end up paying attention to it more when I am switching between three windows and not in a cyle.

I have tried to get this in KDE Plasma 6 (with a global menu bar) and you just can't quite get there, so you have to settle for maximised but not full-screen apps, which is annoying.

I understand the difference and the architectural history that is that "full-screen" on X/Wayland is essentially a kiosk/don't-interrupt-my-game mode, whereas on the Mac it is chromeless windows on a virtual desktop that you can't get stuck in if you forget the restore keystroke.

But it frustrates me I can't get that.

Re: Niri – A scrollable-tiling Wayland compositor

#56

Post by ducktective »

russelg wrote: post #48
ducktective wrote: post #46

Earlier quoted context omitted.

One of the advantages of tilling wm are that every window that is run, is visible too. Nothing invisible exists. But in this "endless horizontal tilling" scheme, the above principle would no longer hold, right?

That typically isn't true in practice right? It's fairly common to have multiple "desktops" when using a tiling WM.

Yes, still on each workspace, everything is visible on i3. I wonder how scroll to the right differs from i3's tabbed panes.

Re: Niri – A scrollable-tiling Wayland compositor

#57

Post by lillecarl »

ducktective wrote: post #46
benoliver999 wrote: post #42

Earlier quoted context omitted.

Yes same here but with i3, I ran it for over 10 years but niri was just an instant 'aha' moment for me. I will say, recent builds have a 'mini map' sort of zoom-out feature that I quite like - my one critique of niri was that I would sometimes get 'lost'.

One of the advantages of tilling wm are that every window that is run, is visible too. Nothing invisible exists. But in this "endless horizontal tilling" scheme, the above principle would no longer hold, right?

No, because every tiling WM has multiple workspaces.

But yes, that wouldn't be true, though focus moves to fresh windows so it's not an issue.

Re: Niri – A scrollable-tiling Wayland compositor

#58

Post by ducktective »

argiopetech wrote: post #51
ducktective wrote: post #46

Earlier quoted context omitted.

One of the advantages of tilling wm are that every window that is run, is visible too. Nothing invisible exists. But in this "endless horizontal tilling" scheme, the above principle would no longer hold, right?

Newly started applications receive focus, so they're visible by default. They are inserted right of the current view, so recovering the previous active pane is consistent ("left pane" keybinding, or the appropriate gesture). Things on other desktops are invisible in every WM. The only difference with niri is the possibility for things to be left or right of the current window. Overview helps with that, but I know wha…

Like imagine editor is on ws2, you open a terminal to /tmp/ to check something quick, it scrolls to the right, then jump to ws3 for your file manager and other stuff and go back to your editor.

Now you want to access that terminal on /tmp/ again. Where was it?

In i3, I just spam-switch workspaces in this case, but at least I can find them. With scrollable wms, every ws can potentially hold that target app.

Re: Niri – A scrollable-tiling Wayland compositor

#59

Post by vergessenmir »

Moved onto Niri yesterday after having to reinstall my PopOS and it just clicked. Like i3wm did all those years ago.

I can focus for hours on end and spend zero mental energy on resizing a window. I had less of that with i3wm but you had to always readjust after a few windows were tiled to your workspace. That final bit of cognitive overload was removed with Niri.

EDIT: Spec: RTX 3090, Pop OS 24.04 (beta), 4K 43" Monitor,

Niri Installed from cargo build, super easy install, make sure you install xwayland-satellite so that you can run VS Code, Obsidian, Zoom, Blender and other strictly X11 applications

Re: Niri – A scrollable-tiling Wayland compositor

#60

Post by evgpbfhnr »

My only complain about niri is that after a few weeks without reboot I end up with ~500 terms open, as I often open a new shell to check something, get distracted, and forget about it as it scrolls out of the view... (I usually notice at the 400-500 mark because this machine starts swapping noticeably, and closing it all is a chore that usually ends in pkill without checking...)

Maybe a bit more self discipline would help :)

Post reply on HN