this post was submitted on 22 Jun 2024
19 points (100.0% liked)
Linux
5372 readers
36 users here now
A community for everything relating to the linux operating system
Also check out !linux_memes@programming.dev
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Automatable (configuration-less) is indispensable. I got used to it with bspwm, and after using that for a while, switched to herbstluftwm and realized I'm stuck. I don't think I can go back to a WM with a configuration file anymore. Even the different between i3 and fully config-less like hlwm is stark once you're on the other side.
What does this mean? You do a manual action once and it always uses that position?
It means that anything you can do, set, or configure in the WM, you can do through a CLI RPC mechanism. There is no configuration file, no custom config syntax. The "config" is just a shell script full of these commands that herbstluftwm calls when it starts. Literally any behavior you can configure or make happen, you can do with these command line calls.