imho both strings "XkbLayout" and "xkb_layout" are ?currently? used. i hope i'm using the right repo. Now i try to checkout what the crazy gnome desktop is doing to my keyboard settings, maybe i switch back to fvwm2...
Cheers, Jens FYI: https://gitlab.freedesktop.org/xorg/driver/xf86-input-keyboard/blob/master/src/kbd.c : Line 78 #endif /* NetBSD */ "XkbRules", "base", "XkbModel", "pc105", "XkbLayout", "us", NULL }; https://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/blob/master/src/xf86libinput.c : Line 1040 rmlvo.layout = xf86SetStrOption(pInfo->options, "xkb_layout", defaults.layout); Am Mi., 2. Jan. 2019 um 00:36 Uhr schrieb Peter Hutterer < peter.hutte...@who-t.net>: > On Wed, Dec 26, 2018 at 11:41:11AM +0100, Jens Harms wrote: > > Hi All, > > please point me to the current "InputClass" documentatation (if > available). > > should be in man xorg.conf, not sure there's more than that short of > google. > > > I tried to configure my keyboard. because setting the option "XkbLayout" > > did not work i was looking at the sources. i did not find any up-to-date > > documentation but found anoying uses of XkbLayout and xkb_layout in > > libinput. evdev is using only "xkb_layout". > > the X server's option parsing code is case-insensitive and ignores > underscores. So XkbLayout and xkb_layout are the same option name, which is > why the libinput driver only parses the latter. Not sure where you found > XkbLayout. git grep shows nothing. > > Anyway. The drivers only do on-plug xkb option setting, if you have a > desktop environment like GNOME it most likely overwrites the xorg.conf > settings on login. > > Cheers, > Peter > >
_______________________________________________ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
