komorebi-application-specific-configuration VS yabai

Haha hello!

I don't use Teams personally but I believe some people have solved this and it is part of the standard application-specific fixes that are used to generate base configurations.[1]

Thanks to the architecture of komorebi, it's pretty easy for users to fix (and then contribute fixes for) weird behaviour of individual apps without touching the source code.

Thankfully an army of dedicated users has congregated on the project Discord so if you ever get stuck with the sort of behaviour you're describing with any application, someone on the server will be able to show you to fix it (and then add the fix to the application-specific fixes repo so future users never have to deal with it).

[1]: https://github.com/LGUG2Z/komorebi-application-specific-conf...

[4] https://github.com/LGUG2Z/komorebi-application-specific-conf...

Introducing a decoupled library of application-specific fixes in YAML that can be used to generate the majority of configuration options for applications that are uncooperative-by-default. The goal is to eventually just be able to run one command to generate 99% of your configuration, leaving you to focus on the other 1% which should essentially be your preferred shortcuts and workspace layout options.

komorebi dev here. I can't tell you the number of times I've wanted to just write my own take on sxhkd[1] for Windows and use that to manage my own keybindings for komorebi instead of ahk.

You can just as easily write your own/use another hotkey daemon or PowerShell scripts to handle komorebi's configuration and keybindings, in that sense there is no dependency on ahk at all. However, the inertia around ahk in the Windows ecosystem is undeniable and it's in the interests of making adoption and onboarding easier that the project provides example ahk files and has invested in an ahk code generation library.

My thoughts on the dominant hotkey daemon in the Windows ecosystem aside, I remain convinced that the famous bspwm socket communication architecture[2] is the best way to handle both configuration and keybindings for a tiling window manager that has been proposed to this today.

Unfortunately I have to concede that there is a certain configuration burden that comes with komorebi, which is amplified in some cases by having to write/maintain ahk. This configuration burden is largely due to the highly fragmented nature of Windows application development that is discussed often on HN and it is inescapable.

With this in mind, the next release of komorebi (currently available on master) will invest even more heavily in automatic configuration generation.

A separate repository of common application-specific configuration tweaks[3] (in YAML!) has been created which I and others from the komorebi Discord server are contributing to, with the goal of having the edge cases for as many applications as possible fully documented so that a comprehensive configuration file can be generated[4] for the user which ensures that every (major) Windows application behaves as expected under a tiling window manager.

I hope that other Windows tiling window manager developers can use these YAML definitions in the future to handle the same edge cases in their projects so that eventually there will be a tiling window manager of every flavour (bspwm, i3wm etc.) available for Windows users where having to manually accommodate and compensate for the non-standard behaviour of individual applications is a thing of the past.

[1]: https://github.com/baskerville/sxhkd

[2]: https://github.com/baskerville/bspwm#description

[3]: https://github.com/LGUG2Z/komorebi-application-specific-conf...

[4]: https://github.com/LGUG2Z/komorebi/#generating-common-applic...

It exists! Check out [yabai](https://github.com/koekeishiya/yabai), which is nicely paired with [skhd](https://github.com/koekeishiya/skhd).

I have a 49 inch CRG9 and the best recommendation for window management is Yabai (https://github.com/koekeishiya/yabai) along with skhd (https://github.com/koekeishiya/skhd). Yabai is a greedy window management solution that tries to fit opened applications in given space and skhd let's you easily jump between those using keyboard shortcuts. This has massively improved my ultrawide experience.

Only disclaimer is, configuring yabai has a slight learning curve.

Want something free that's better than tiling on Windows? Yabai.

Here it is. There is no visualization of the stack, which apparently Stackline in the other comment supports, but I don't tend to need that. Just being able to move between the windows is good enough for me.

https://github.com/koekeishiya/yabai/issues/203#issuecomment...

I use Yabai on my Macs without SIP enabled. Here’s a list of the features that absolutely require SIP to be disabled: https://github.com/koekeishiya/yabai/issues/1863

But you don’t need to disable SIP just for tiling.

> there's still a ton of tinkering and tweaking you need to do to get Yabai really working correctly

This is pretty much true of basically every tiling window manager on Linux, too.

For me, using Nix-Darwin for MacOS and NixOS has drastically simplified my tiling window manager setup after initially doing the work to figure out my ideal config.

SIP is a feature that protects you from malicious actors with root (admin) access on your device. After they've encrypted your photos and drives and changed your passwords, it prevents them from making your machine unbootable by deleting or altering system binaries. As a side effect of this protection, you give up certain freedoms to customize your system.

https://github.com/koekeishiya/yabai

For instance requires SIP to be disabled.

This is disproven by the fact that Yabai [1] can instantly swap spaces with SIP disabled.

[1] https://github.com/koekeishiya/yabai

If you find the native window management lackluster (like I do), you can install a window manager like Amethyst, or yabai, veeer, or many others.