![]() ![]() Keysym and corresponding string is what the client obtained using XLookupString(3) and friends. Keycode together with the state value is what X sends to the application in XKeyEvent(3) structure. The state represents modifier keys, 0x01 is Shift. Keycode 21 is what input device supplied to X, typically a physical key index of some sort. Note keycode 21, state 0x1 and keysym 0x2b aka plus. State 0x1, keycode 21 (keysym 0x2b, plus), same_screen YES, $ xev -event keyboard KeyPress event, serial 45, synthetic NO, window 0x2200001, Use xev (package xorg-xev) to get keycodes and to check how your keymap works. The core XKB functionality is quite simple, and it is necessary to have an idea on how it works before working on the keymaps. Also, there is no problem changing XKB configuration while X is running. Note that unlike standard system-wide configuration via nf(5), this is a per-user keymap. Test -f ~/.Xkeymap & xkbcomp ~/.Xkeymap $DISPLAY Once the layout is ready, save it as ~/.Xkeymap and make ~/.xinitrc load it on startup: It will, however, check the syntax and report errors. xkm file, without uploading anything to the server. Note that without $DISPLAY argument xkbcomp(1) will try to compile. ![]() To upload the data back to the server, run Use xkbcomp(1) (package xorg-xkbcomp) to manipulate XKB data. ![]() Note: Even if you faithfully recreate a working setxkbmap(1) command as an Xorg configuration file, it might not take effect at all due to Xorg bugs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |