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
To what extent would it be possible to make X11 an optional dependency for keyleds?
I'm having a blast with its current use, however it would be nice to have the effects persist in a TTY since this is usually what I log into and work with. I ask more for my own curiosity rather than suggesting a change, since I'm not too familiar with the X11 library (or X11 in general) or the structure of your project.
Thanks!
The text was updated successfully, but these errors were encountered:
For getting context information from the windows manager (X atoms on the root window, specifically). That's how it knows the current active window.
For keypresses through XInput2.
So in the current design, cutting X11 dependency would mean it can no longer detect context changes (which is not an issue in a tty I guess), nor could it detect keypresses (which might be more problematic).
The issue for keypresses is to get them straight from the device, keyleds would need root access. And it was a major design decision early on to run as a regular user. Nothing is impossible, but adding a root mode and evaluating the security implications would definitely be low priority.
Yet I could totally see someone using keyleds without keypresses. You could, for instance, have your shell send context information to keyleds manually through a dbus notification, kind of like console applications get title notifications. As long as not reactive effect is desired it could work.
To what extent would it be possible to make X11 an optional dependency for keyleds?
I'm having a blast with its current use, however it would be nice to have the effects persist in a TTY since this is usually what I log into and work with. I ask more for my own curiosity rather than suggesting a change, since I'm not too familiar with the X11 library (or X11 in general) or the structure of your project.
Thanks!
The text was updated successfully, but these errors were encountered: