Explain format further.

Frsf Nrrg 2018-06-12 19:41:11 +00:00
parent cb4e5333d1
commit 4a440c8d31

@ -7,8 +7,11 @@
(`Shift`=`0x01`, `Lock`=`0x02`, `Ctrl`=`0x04`, `Mod1`=`Alt`=`0x08`, `Mod2`=`0x10`, `Mod3`=`0x20`, `Mod4`=`0x40`, `Mod5`=`0x80`). These names should not be confused with the keys whose (`Shift`=`0x01`, `Lock`=`0x02`, `Ctrl`=`0x04`, `Mod1`=`Alt`=`0x08`, `Mod2`=`0x10`, `Mod3`=`0x20`, `Mod4`=`0x40`, `Mod5`=`0x80`). These names should not be confused with the keys whose
pressing might produce the modifier; on US keyboards, keysym `Alt_L` (keycode 64) and keysym `Alt_R` (keycode 108) both produce the `Alt` modifier. pressing might produce the modifier; on US keyboards, keysym `Alt_L` (keycode 64) and keysym `Alt_R` (keycode 108) both produce the `Alt` modifier.
`<Keysyms>` is a nonempty `+` separated list of keysym names, case insensitive (so that `A` and `a` are both assumed to be lowercase `a`.)
The binding specifications here mostly overlap with those from i3 (see https://i3wm.org/docs/userguide.html#keybindings). `<Keycodes>` is a nonempty `+` separated list of xkbcommon keycode ids, typically an integer between 9 and 255, although possibly much larger.
The binding specifications here mostly overlap with those from i3 (see https://i3wm.org/docs/userguide.html#keybindings). Currently XKB layout specifiers are not supported.
### How to identify keys ### How to identify keys