autorandr VS bspwm

could use the postswitch hook provided by autorandr, though this would require letting autorandr manage your display layout as well: https://github.com/phillipberndt/autorandr

autorandr worked great for me for hot plugging when I would frequently use my laptop with two external monitors.

Autorandr does run in the background as it is a daemon. For systemd integration see https://github.com/phillipberndt/autorandr/blob/master/contrib/systemd/autorandr.service

I use autorandr (https://github.com/phillipberndt/autorandr) to load display configurations with a hotkey. I'm 100% sure there is a "better" way of doing so over my setup.

If your using X11, try autorandr. It's a bit clunky for me with the windows moving around after waking up but they eventually find where they're supposed to be... mostly.

I would suggest taking a look at something like autorandr to help dynamically adjust your settings when you connect/disconnect.

There's also autorandr that allows you to save monitor setups and automatically switch between them as you connect/disconnect displays

autorandr (link) (xorg)

No, but you can save settings to script and run on login. Arandr does it with GUI. Autorandr automates and manages multiple setups.

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