65
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 23 Jun 2026
65 points (100.0% liked)
Linux
65961 readers
329 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 7 years ago
MODERATORS
If there's still wayland protocol extensions required for this functionality (which I don't think, kwin should have everything it needs, protocols would only be necessary if you'd want a DE-agnostic client application to manage the hotkeys), then KDE is in the best position to get things moving. With wayland development, nothing gets done without a reference implementation and vote from a big compositor, so sitting back and waiting "until things improve" is rarely a valid strategy.
I don't know about the accessibility side of this, but from how uninterested the devs are every time it's brought up I can only assume that a keyboard-centric workflow is no longer a focus for KDE. Which is a shame, because with
khotkey, KDE previously did provide the best experience out of all major DEs. Now it's down among worst, when even Gnome(!) has retained some kind of custom hotkey functionality on wayland.It's tightly interconnected with accessibility because alternative input systems, like eye gaze input, macros to expand text, and other accessibility tools for alternative input hardware all friends in the same types of window-agnostic input interacting. (Similarly for output hardware, I think?)
Like, custom text replacement with XCompose breaks because of how Wayland "silos" programs, which is why ~/.XCompose files only partially work in KDE Plasma. If Wayland/KDE fully implemented accessibility tools, then it would be possible to solve all of these problems.
Or, at least, that's my layman's understanding of the situation.