diff options
author | Christian Duerr <chrisduerr@users.noreply.github.com> | 2018-10-16 18:46:26 +0000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2018-10-16 18:46:26 +0000 |
commit | a727801f60286282795e850637de7e21f15d4114 (patch) | |
tree | fe2660439e54de2fb4419ae9e4132fb995a8d148 /alacritty.yml | |
parent | 15e0deae2b49078b47a782679300cdf99d9ce687 (diff) | |
download | alacritty-a727801f60286282795e850637de7e21f15d4114.tar.gz alacritty-a727801f60286282795e850637de7e21f15d4114.zip |
Allow the usage of scancodes in the config
This change should allow the usage of scancodes in the configuration
file.
When a VirtualKeyCode for glutin is not present, this should now allow
the user to use the scancodes instead. If the user specifiecs a key with
its scancode even though the key has a VirtualKeyCode, it should still
work.
The behavior of directly specifying a VirtualKeyCode should be unchanged
by this.
This fixes #1265.
Diffstat (limited to 'alacritty.yml')
-rw-r--r-- | alacritty.yml | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/alacritty.yml b/alacritty.yml index 11a9e6ae..63bb7a4b 100644 --- a/alacritty.yml +++ b/alacritty.yml @@ -324,6 +324,12 @@ live_config_reload: true # A full list with available key codes can be found here: # https://docs.rs/glutin/*/glutin/enum.VirtualKeyCode.html#variants # +# Instead of using the name of the keys, the `key` field also supports using +# the scancode of the desired key. Scancodes have to be specified as a +# decimal number. +# This command will allow you to display the hex scancodes for certain keys: +# `showkey --scancodes` +# # Values for `mods`: # - Command # - Control |