alacritty / alacritty/alacritty

key bindings in windows (mapping Ctrl+Space)

Ouverte
#1,703 63 commentaires 8 réactions 0 personnes assignées Voir sur GitHub
A - deps H - windows S - input
Langage dominant
Rust
Étoiles
65.7k
Forks
3.6k
Merge moyen
3 h 5 min
PR mergées (30 j)
3

Description

Using alacritty (downloaded from the appveyor link) on windows and have some issues/questions about key bindings.

1. bash shortcuts using Alt key are not working - is this expected?
I added a few mappings to the config file that gets me some of what I most commonly use, but however I still miss several other important ones that I don't know how to map (`Alt+.` for instance, and others).
Should this work out of the box, or if not, can a canned list of such mappings be made available for those who might want to add it to their configs optionally.
One I sorely miss and don't know how to map is `Ctrl+Alt+e` which binds to expanding aliases.
```
- { key: D, mods: Alt, chars: "\x1bd" }
- { key: B, mods: Alt, chars: "\x1bb" }
- { key: F, mods: Alt, chars: "\x1bf" }
```
2. In tmux I use Space as my prefix key.
`set -g prefix C-Space`
I've tried different things (blindly) in the config file and couldn't get this to work.
Any pointers on how to achieve this mapping?

Off topic, but on windows, alacritty doesn't honor any of the command line arguments for me. I've seen other folks refer to using this even on windows, so somehow it is specific to my setup I assume. i.e. if I run `alacritty.exe -vvv` it spawns the terminal but there is no debug output, or if I do `alacritty.exe --help` the command just returns without any output.

Thanks!

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.