Destroyed Unmapped keybindings: using a keycode (markdown)
parent
4cb261a7fb
commit
53b006dd41
|
@ -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" }
|
||||
```
|
Loading…
Reference in New Issue