undefined | Better HN

0 pointsducktective5mo ago0 comments

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?

0 comments

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.

squigz5mo ago

I might give Niri a shot at some point, but yes, this is my thought too: this is more or less the same as having multiple tabbed panes, which enables the grouping GP refers to.

1 more reply

argiopetech5mo ago

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.

ducktectiveOP5mo ago

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.

argiopetech5mo ago

It's right of your editor, where it started.

If you have (having had "Editor" focused, and just opened "TermT"):

  Editor | (TermT) | Term | Browser
  (FM) | Term | Browser | etc.

(where pipe delimits a pane and parens are the active pane), if you go "next desktop" from "TermT" (the terminal at /tmp), that moves you down the stack of desktops. Moving up the stack of desktops returns with focus on "TermT". You'd then go "left pane" from "TermT" to get back to the editor.

The answer (for me) is to think of desktops as topics. The terminal on /tmp is with the things that prompted its creation. If I needed to check some log output, for example, it's with the project that made that log output.

Edit: Note that there's nothing keeping you from stacking those terms if you like, i.e., the appropriate keybinding goes from the previous to

  Editor | (TermT), Term | Browser
  (FM) | Term | Browser | etc.

where the terms stack vertically in the ribbon of the desktop.

1 more reply

atlintots5mo ago

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).

argiopetech5mo ago

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.

WhyNotHugo5mo ago

Tiling window managers have tabs, so not all windows are visible.

You can see window titles on the tabs on the tab bar, but you can’t even see the title of windows which are in a split container of a background tab.

Shebanator5mo ago

Tabs, and workspaces.

lillecarl5mo ago

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.

j / k navigate · click thread line to collapse

0 comments

russelg5mo ago

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

ducktectiveOP5mo ago

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

squigz5mo ago

I might give Niri a shot at some point, but yes, this is my thought too: this is more or less the same as having multiple tabbed panes, which enables the grouping GP refers to.

1 more reply

argiopetech5mo ago

Things on other desktops are invisible in every WM.

ducktectiveOP5mo ago

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.

argiopetech5mo ago

It's right of your editor, where it started.

If you have (having had "Editor" focused, and just opened "TermT"):

  Editor | (TermT) | Term | Browser
  (FM) | Term | Browser | etc.

Edit: Note that there's nothing keeping you from stacking those terms if you like, i.e., the appropriate keybinding goes from the previous to

  Editor | (TermT), Term | Browser
  (FM) | Term | Browser | etc.

where the terms stack vertically in the ribbon of the desktop.

1 more reply

atlintots5mo ago

argiopetech5mo ago

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

WhyNotHugo5mo ago

Tiling window managers have tabs, so not all windows are visible.

You can see window titles on the tabs on the tab bar, but you can’t even see the title of windows which are in a split container of a background tab.

Shebanator5mo ago

Tabs, and workspaces.

lillecarl5mo ago

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.

j / k navigate · click thread line to collapse