mirrors/kitty
1
0
Fork 0
mirror of https://github.com/kovidgoyal/kitty synced 2026-07-26 10:12:17 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update list of GLFW keys in the doc to use kitty's forked GLFW

Browse Source
This commit is contained in:
Kovid Goyal
2020-02-17 17:52:35 +05:30
parent 0285f5a1ad
commit 7928fff645
1 changed files with 8 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
kitty/config_data.py
View File

@@ -84,19 +84,21 @@ as color16 to color255.''')
'shortcuts': [ 'shortcuts': [
_('Keyboard shortcuts'), _('Keyboard shortcuts'),
_('''\ _('''\
For a list of key names, see: :link:`GLFW keys For a list of key names, see: :link:`the GLFW key macros
<https://www.glfw.org/docs/latest/group__keys.html>`. The name to use is the part <https://github.com/kovidgoyal/kitty/blob/master/glfw/glfw3.h#L349>`.
after the :code:`GLFW_KEY_` prefix. For a list of modifier names, see: The name to use is the part after the :code:`GLFW_KEY_` prefix.
For a list of modifier names, see:
:link:`GLFW mods <https://www.glfw.org/docs/latest/group__mods.html>` :link:`GLFW mods <https://www.glfw.org/docs/latest/group__mods.html>`
On Linux you can also use XKB key names to bind keys that are not supported by On Linux you can also use XKB key names to bind keys that are not supported by
GLFW. See :link:`XKB keys GLFW. See :link:`XKB keys
<https://github.com/xkbcommon/libxkbcommon/blob/master/xkbcommon/xkbcommon-keysyms.h>` <https://github.com/xkbcommon/libxkbcommon/blob/master/xkbcommon/xkbcommon-keysyms.h>`
for a list of key names. The name to use is the part after the :code:`XKB_KEY_` for a list of key names. The name to use is the part after the :code:`XKB_KEY_`
prefix. Note that you should only use an XKB key name for keys that are not present prefix. Note that you can only use an XKB key name for keys that are not known
in the list of GLFW keys. as GLFW keys.
Finally, you can use raw system key codes to map keys. To see the system key code Finally, you can use raw system key codes to map keys, again only for keys that are not
known as GLFW keys. To see the system key code
for a key, start kitty with the :option:`kitty --debug-keyboard` option. Then kitty will for a key, start kitty with the :option:`kitty --debug-keyboard` option. Then kitty will
output some debug text for every key event. In that text look for ``native_code`` output some debug text for every key event. In that text look for ``native_code``
the value of that becomes the key name in the shortcut. For example: the value of that becomes the key name in the shortcut. For example: