VirtualDesktop VS komorebi-application-specific-configuration

Not strictly AHK related, but I have a small script that uses VirtualDesktop by MScholtes to manage my virtual desktops. Nothing fancy atm, just ctrl+alt+numpad to change desktops. But I do have a problem, I can't always remember which desktop has what stuff in it! So I was wondering if there is something like win+tab that gives a preview of what there is in each desktop.

This plus Autohotkey or something like that

This can do it from a batch file -> https://github.com/MScholtes/VirtualDesktop

Pardon me, for not getting back to your in a more timely manner. hecktick weekend. Escaping characters is always a PITA no matter the language, in the case of AHK escaping quotes is awful as you escape a quote with a quote. Would believe if I told you I spent an entire day on just to realise this, between powershell and Autohotkey. I am very glad to know the feeling is mutual and it was not just me being stupid imo. Your solution was just what I needed, I am soon to be among one of the cool kids. Also that Function is amazing! Now, as powerful as PowerShell is (pun intended), is super slow compared to AHK (being a wrapper around .NET, worst if is the first run) and AHK can do most of what PS does: I did not know this, makes sense though. This was mostly an exercise on trying to do the things AHK does really well with PowerShell and just generally future prosperity between AHK and PowerShell interoperability. Text: awful virtual desktop feature really well. There was this AHK script that did this too but it got broken due to API changes in windows 11. This the module

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...