3 ms·
For me, one of the biggest motivations in writing komorebi was that I wanted to separate the window management from the key binding and shortcuts using a messag
by bsnnkv 4y ago
For me, one of the biggest motivations in writing komorebi was that I wanted to separate the window management from the key binding and shortcuts using a message-passing architecture similar to bspwm and yabai.
By exposing all of the functionality (aka socket messages) via a cli (komorebic), I can use whatever I want to handle my shortcuts, which in turn makes it easy to configure my shortcuts to whatever I want. An added bonus is that exposing the functionality via the cli means that I can compose multiple commands to run sequentially with a single key bind.
- naikrovek 4y agothat is indeed a good feature.
- comfypotato 4y agoRead this whole page looking for this thought exactly, and it’s convinced me to try it. Can you give some insight in how maintained komorebi will be? I know you can’t predict the future, I’m just curious to what extent you prioritize it.
- bsnnkv 4y agoFor the most part I consider komorebi to be pretty feature-complete as a tiling window manager. That being said, I use it extensively every day myself so I'm constantly fixing any bugs that I come across myself in daily use, and similarly I'm always playing with new ideas and coming up with features that I have not seen present in other twms.