xmonad VS i3

And here is my Xmonad configuration

xmonad

Here is another tiling wm with screenshots: https://xmonad.org/

xmonad https://github.com/xmonad/xmonad

As far as wms go, I always liked fluxbox and xmonad. Openbox has its fans, and i3 is very popular. I prefer a de over a wm but I know a lot of people use i3.

How are you installing the xmonad code that you try to build? Have you cloned https://github.com/xmonad/xmonad and https://github.com/xmonad/xmonad-contrib into your ~/.xmonad directory, and then running stack init?

You can install xmonad 0.17 from source. There's a few ways of doing that, check the installation guide, most are quite straightforward.

I had little success with manual splits because I was busy resizing most of the time. Therefore the idea with windows that are always as big as their content. The code for the windows is already built so that the logic per tab is interchangeable, how the windows should behave. You just have to implement more layouts, as I call them. The concept comes from Xmonad. In this link you can see examples when you scroll down to "Layouts": https://hackage.haskell.org/package/xmonad-contrib

I started off using i3wm a while back which made the migration to swaywm pretty seamless. Most of the migration/config was finding wayland-native alternatives for various utilities (screenshot, notification daemon, some applications) but there are lots of helpful blog posts (below).

i3 is probably the most well-documented and well-supported, and has a pretty simple configuration syntax.

Since Sway is a port of https://i3wm.org/ to Wayland, for enlightening I suggest you look for info on the latter.

i3wm.org

> Dock to a different dock (hot-desking; same brand and size of monitor) and the entire display options need to be re-written - no option to preserve it

Does anything do this properly? I use i3[0], and wrote some super janky automation to preserve my layouts when I switched from dock to no dock and back. It has the concept of layouts that can be stored/loaded. So I had a script that would dump the layout, I had to manually run it before disconnecting (couldn't figure out how to detect the monitor disconnect and dump the layout before i3 re-arranged everything). And another script that would load the layout when new monitors were connected (this was easy enough).

I'd be _really_ impressed if something did this correctly without any user hacking.

[0] https://i3wm.org/

There’s a GitHub issue for this vertical bars. It sounds complicated.

https://github.com/i3/i3/issues/1129

Yup! We even have an FAQ entry on the reasons for not merging features without careful consideration: https://faq.i3wm.org/question/778/why-is-patch-not-merged-an...

Also, saying “it’s not that many lines of code” comparing the before and after state is too simplistic: it doesn’t include the cost of changing the existing code into the desired state, which can be a significant effort, even if the number of lines doesn’t differ much before and after. See https://github.com/i3/i3/pulls?q=is%3Apr+author%3Astapelberg... to get an impression of how much work it was to merge gaps.

Yeah this is Artix linux with I3WM window manager.

hi, by i3 you meant this ? https://i3wm.org/