From 53b006dd41f9e8f7a33cfef48e80fa8aa0a2bb60 Mon Sep 17 00:00:00 2001 From: Christian Duerr Date: Thu, 7 Mar 2019 21:02:54 +0000 Subject: [PATCH] Destroyed Unmapped keybindings: using a keycode (markdown) --- Unmapped-keybindings:-using-a-keycode.md | 14 -------------- 1 file changed, 14 deletions(-) delete mode 100644 Unmapped-keybindings:-using-a-keycode.md diff --git a/Unmapped-keybindings:-using-a-keycode.md b/Unmapped-keybindings:-using-a-keycode.md deleted file mode 100644 index a3d6e9a..0000000 --- a/Unmapped-keybindings:-using-a-keycode.md +++ /dev/null @@ -1,14 +0,0 @@ -While trying to bind some specific keys in `alacritty`, you might realize that some keys are not defined in the [source code](https://github.com/jwilm/alacritty/blob/master/src/config/mod.rs#L2290). This is an issue from the dependency [winit](http://github.com/tomaka/winit#600). - -However, you can still remap them using their keycode. Find your keycode with `showkey --scancodes` or `alacritty --print-events` and add it to your config file. - -For example, `Ctrl` + `>` (`>` being accessed as `Shift`+`.`) will be shown as `0x34` by `showkey -scancodes` and `alacritty --print-events` will print: -``` -input: KeyboardInput { scancode: 52, state: Pressed, virtual_keycode: None, modifiers: ModifiersState { shift: true, ctrl: true, alt: false, logo: false } } } } -``` - -You can then bind `Ctrl` + `>` as -```yaml -key_bindings: - - { key: 52, mods: Shift|Control, chars: "action" } -``` \ No newline at end of file