You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Another excellent keymap utility, Kanata, exposes a TCP server that allows the user to set the active layer by sending a JSON message of the form: {"ChangeLayer":{"new":"new-layer-name"}}.
This opens a world of possibilities by allowing external daemons to dynamically change the active layer. This enables things like application-specific keybinds (see 1, 2, 3) without burdening kmonad devs. I've bounced back and forth between Kmonad and Kanata but ultimately the application-specific binds were the deciding factor.
Would implementing some sort of API be possible?
The text was updated successfully, but these errors were encountered:
Another excellent keymap utility, Kanata, exposes a TCP server that allows the user to set the active layer by sending a JSON message of the form:
{"ChangeLayer":{"new":"new-layer-name"}}
.This opens a world of possibilities by allowing external daemons to dynamically change the active layer. This enables things like application-specific keybinds (see 1, 2, 3) without burdening kmonad devs. I've bounced back and forth between Kmonad and Kanata but ultimately the application-specific binds were the deciding factor.
Would implementing some sort of API be possible?
The text was updated successfully, but these errors were encountered: