i3-auto-layout VS bspwm

The problem with this fairly complex solution is that the easier path by far is simpler window arrangements, multiple monitors, and many workspaces. Once you have more windows than fit on a workspace its easier just to have more workspaces and 1-3 windows is what basically universally fits on most monitors.

If you organize more things in the same space you probably need indivdual apps that themselves have tabs like browsers, editors, IDEs rather than more windows.

Personally I use https://github.com/chmln/i3-auto-layout to make slightly better layouts automatically be automatically alternating between v and h splits and find this fits my needs 95% of the time.

Shit work under i3 is already very small but if you wanted to reduce it further I think you could probably go a long way with a very simple feature.

Add a save button that saves current layout to a list like so

Browser, calculator

Browser, pdf reader

terminal terminal terminal

ide terminal terminal

Then have a restore function that simply walks the list finds the entry that matches the kind and number of window and shoves existing windows into that layout. You can at creation time use something like i3-save-tree, edit the json, yada yada but its all fairly manual and I think for the use case it would be relatively simpler. The few non standard all match for me a simple pattern eg there really isn't 2 different ways I want IDE terminal terminal

i3-auto-layout is faster and less resource usage

Bspwm is a window manager. Configuration happens in $XDG_CONFIG_HOME/bspwm/bspwmrc, as per stated here: https://github.com/baskerville/bspwm

Use BSPWM. It supports right clicks by default and its modular. You might want to look for status bars that work with it, slstatus does not work. Good luck, supremacist!

I had not heard of bspwm but I am a fan of telling WMs. Looking at the documentation now, I really like the pragmatic approach lol https://github.com/baskerville/bspwm

If you use the bspwm off of github instead of the old 0.9.10, you can use bspc node @parent -y next to cycle the split type of the parent of the focused. I added it ~1.5years ago, after baskerville added node -y horizontal and node -y vertical to set the split type of a node to vertical/horizontal ~2 years ago.

Also bspwm's JSON generation and parsing is not great. If you have a window with quotes in its class name, bspwm, when dumping it, will not escape them generating invalid JSON (e.g. {"className":"the "cool" window",) that jq will not be able to read, and even worse, bspwm itself will not be able to read. (Yes, if a window's class name contains a " character, bspwm will fail to reload after you run wm -r #1362).

Just follow this guide

Pencere yöneticisi: bspwm