it’s amazing what people will do to get the tiling stuff i’ve had via an AutoHotKey script for … feels like a decade, but i don’t know how long i’ve had it. I didn’t come up with it, but i collaborated a little.
it’s designed for a single high res monitor (1440p or better) and multiple monitors aren’t supported at all. i haven’t added that because i don’t need that.
the Windows 11 mouseover-the-maximize/restore-button beats my thing on usability, though.
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.
Read 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.
For 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.
https://gist.github.com/naikrovek/b13a77d169de0e192bcf48fec0...
it’s designed for a single high res monitor (1440p or better) and multiple monitors aren’t supported at all. i haven’t added that because i don’t need that.
the Windows 11 mouseover-the-maximize/restore-button beats my thing on usability, though.