61–70 of 84 posts
Recent versions of KDE have pretty good tiling support, so it's possible to have a rich DE and good tiling.
when you say tiling support, do you mean automatic tiling, or sending it to a corner via key combo?
Essentially turning kwin into a tiling WM
It is like when you buy an appliance and it just fades into the background and then, one day, you realize you've had it for 10 years without any problems and you feel a tinge of gratitude before moving on with your day.
Is the author saying that until 2019 they used Linux on the desktop without using X?
Earlier quoted context omitted.
Apart from the Haskell fun, xmonad is really really good. Especially how it handles workspaces on multiple monitors. By default, each monitor has one workspace. Not one workspace for ALL monitors. So if your side screen has say documentation open, and you switch on your main screen from terminal to editor, only the main screen changes. The side screen stays untouched. Some people prefer it, some hate it. But it's goo…
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.…
No, it doesn't seem that way. The Niri manual says each monitor has an independent set of workspaces. In XMonad there is one shared set for all monitors, but each monitor independently shows one of those workspaces.
(If the user tries to show on monitor A the workspace currently visible on monitor B the two monitors swap their workspaces.)
Configuring your WM in Haskell seems fun, but I suspect "fun" is the primary motivator, not any kind of practical reason. Type-checking keybindings is cute, but you're going to discover that the keybinding doesn't work when you go to use it, so how much time are you really saving? That's not helped by the fact that many WMs/compositors have validators for their configs, so you're getting much of the same benefit with…
Apart from the Haskell fun, xmonad is really really good. Especially how it handles workspaces on multiple monitors. By default, each monitor has one workspace. Not one workspace for ALL monitors. So if your side screen has say documentation open, and you switch on your main screen from terminal to editor, only the main screen changes. The side screen stays untouched. Some people prefer it, some hate it. But it's goo…
This is the reaon I use XMonad, and I hate how this one design choice that only one window manager has gotten right is what locks me into X11. If anyone ever learns of a non-X11 window manager that handles workspaces on multiple monitors the XMonad way, contact me!
I started with i3 and really like the keybindings. A couple months later I found out about xmonad through general interest in the subject. I installed it, found someone's config to use i3 keybinds (which I was used to at that point) and had a lot of fun. It's definitely quick as heck and I like how compact the codebase is for edits. Plus, it gave me an excuse to learn some rudimentary Haskell.
My visual setup is always SUPER minimal, as it comes out of the box. So that was nice.
Unfortunately I had some serious trouble with X11 and an app my workflow relies on running in wine, so I switched to sway for Wayland (such as it is it fixed the issue). I know some folks from the xmonad community are trying to implement it over Wayland [0], and were it to come to fruition it would be a VERY welcome development.
[0] https://discourse.haskell.org/t/xmonad-for-wayland-call-for-...
Earlier quoted context omitted.
Apart from the Haskell fun, xmonad is really really good. Especially how it handles workspaces on multiple monitors. By default, each monitor has one workspace. Not one workspace for ALL monitors. So if your side screen has say documentation open, and you switch on your main screen from terminal to editor, only the main screen changes. The side screen stays untouched. Some people prefer it, some hate it. But it's goo…
> xmonad is really really good. Especially how it handles workspaces on multiple monitors This is the reaon I use XMonad, and I hate how this one design choice that only one window manager has gotten right is what locks me into X11. If anyone ever learns of a non-X11 window manager that handles workspaces on multiple monitors the XMonad way, contact me!
Earlier quoted context omitted.
Apart from the Haskell fun, xmonad is really really good. Especially how it handles workspaces on multiple monitors. By default, each monitor has one workspace. Not one workspace for ALL monitors. So if your side screen has say documentation open, and you switch on your main screen from terminal to editor, only the main screen changes. The side screen stays untouched. Some people prefer it, some hate it. But it's goo…
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.…
Tiling WMs are dead. Long live tiling WMs. Scrolling WMs like Niri/Paperwm are where it’s at now.
Totally agree. I had been using Sway for a few years and tried Niri on a whim. Expected to quickly dismiss it, but ended up being a convert. It's just easier to configure your windows in a useful way, and often the "right thing" just happens by default.