sxhkd VS ly

Hello, firstly I would separate all these non wm related keybindings to a program like sxhkd (https://github.com/baskerville/sxhkd) it's config is easier to modify on the fly and less bloat/unrelated stuff in window managers codebase is always better.

After getting frustrated trying to update the library generation code to conform to the AHK2 syntax changes, I decided to run with an idea that I've had for a while now: writing my own simple hotkey daemon for windows based on skhd and sxhkd.

For GUI automation and the like, I would recommend checking out xdotool and maybe sxhkd for keybinds -- though, each DE/WM tends to have some method of handling keybindings in its own way.

You control shod via a remote controller, called shodc. You map shodc calls to keybindings using a third application (a keybinder like sxhkd).

That said, if you enable linux app support, you can use something like sxhkd for hotkey definitions in combination with bash scripting.

Not that I know, at least the general syntax is said to work with KEYSYMs only. However! I've been reading some more about it and you can try this: if you're not using a US layout keyboard, start sxhkd -m 1 as described here https://github.com/baskerville/sxhkd/issues/249. And just out of curiosity, maybe you can check if you have the proper drivers installed (again, sorry I don't know the details) but at least I have xf86-input-libinput installed.

Because we specify super/ctrl/alt as modifiers x11 doesn't distinguish between left and right. See https://github.com/baskerville/sxhkd/issues/89

Now I have an script that copy the char to the clipboard when I press that shortcut. This is archived using [sxhkd](https://github.com/baskerville/sxhkd). Is there a better way?

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

x11-misc/ly::gentoo-zh Ly - a TUI display manager (https://github.com/nullgemm/ly)

After building & installing ly demonstrate manager (https://github.com/nullgemm/ly) i can't‏‏‎‏‏‎‏‏‎‏‏‎­seem to start it as there is no entry in /etc/sv to start. I then came across this: https://github.com/drozdowsky/ly-void. A build of ly that supports runit & sure enough it has a service to start however when i restart my pc and ly display manager starts, even with the right credentials it does not log in, only turning off my monitor for a moment then booting back into the display manager screen. This is the case for starting my window manager, starting my .xinitrc however it can successfully start the shell. Any help would be greatly appreciated to either start the official build, or to correct the modified one.

I definitely know what you mean; I used to use ly (and haven't been able to figure out how to write a package/service for it, yet) and would love to use that, again.

Here is link number 1 - Previous text "ly"

Yes, actually! Ly is a console-based display manager that allows you to select your login target between any of the standard sessions (KDEs, GNOMEs, and what have you), explicit launching of .xinitrc, or just dropping straight into terminal.

What DM are you using? I tried to compile both ly-void and normal ly according to this guide.

See here how Ly helps fish source the needed files: https://github.com/nullgemm/ly/blob/master/res/xsetup.sh