https://bugs.kde.org/show_bug.cgi?id=460694
--- Comment #3 from ninj...@gmail.com ---
My knowledge of XKB is quite limited. Anyway:
What is the reason for changing CAPS to an additional Super? Is it just to get
rid of unwanted CAPS functionality before applying your xmodmap configuration?
Note that capslock(super) (in /usr/share/X11/xkb/symbols/capslock) does:
hidden partial modifier_keys
xkb_symbols "super" {
key <CAPS> { [ Super_L ] };
modifier_map Mod4 { <CAPS> };
};
which adds CAPS to mod4 modifier. Instead changing CAPS to e.g. an additional
backspace would do:
hidden partial modifier_keys
xkb_symbols "backspace" {
key <CAPS> { [ BackSpace ] };
};
which doesn't do that.
So, for your use case, it seems that enabling "Make Caps Lock an additional
Backspace" instead of "Make Caps Lock an additional Super" would work.
Of course, the "clean" way to do this without xmodmap hackery would be to add
an option in /usr/share/X11/xkb/symbols/capslock to make Caps Lock an
additional Meta, add it to /usr/share/X11/xkb/rules/evdev and
/usr/share/X11/xkb/rules/base (and the corresponding description for GUI
programs to use in evdev.xml, evdev.lst, base.xml and base.lst) and maybe send
a merge request to
https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/
--
You are receiving this mail because:
You are watching all bug changes.
