On 17/12/20 5:50 π.μ., Peter Hutterer wrote:
setxkbmap -print doesn't use the keymap directly as you'd expect. it uses
the RMLVO properties, changing a keymap directly with xkbcomp isn't
reflected in the setxkbmap output. so simply said: this is a false negative.
Why xkbcomp doest seem to wo
$ setxkbmap -layout us,gr,de
$ setxkbmap -print
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete+ledscroll(group_lock)" };
xkb_symbols { include
"pc+us+gr:2+de:3+inet(evdev)+group(c
Sorry my first 'reading on Peter's answer wasnt correct.
I wrote :
> But this isnt what Peter said. It
was a false interpretation of mine.
setxkbmap -print CAN display the current xkeymap (in Ktcsg format ) but only
if the change happened from setxkbmap
