Closed jujpenabe closed 9 months ago
You should make sure that your terminal "hears" whatever keybindings you're trying to assign. You do this with the command keybindings listen
and then hitting the key combination.
You should make sure that your terminal "hears" whatever keybindings you're trying to assign. You do this with the command
keybindings listen
and then hitting the key combination.
I checked the key combinations heard by the terminal and surprisingly the combination control + shift + tab returns nothing.
Control + shift is heard with a different key code than tab ('L') but only the control modifier is heard.
Other modifiers are heard (control + tab, shift + tab) But the reedline keybind doesn't work with those either.
You might try and enable the kitty protocol in the config.nu
use_kitty_protocol: true # enables keyboard enhancement protocol implemented by kitty console, only if your terminal support this.
Different terminals hear different things. This is from WezTerm on Windows.
That solves the problem, now all keybinds work as expected, thanks! I thought the Kitty protocol was exclusive to the Kitty terminal.
I thought the Kitty protocol was exclusive to the Kitty terminal.
Nope. It's exclusive to terminal that support the kitty protocol, which there are a few already. Although I can't name them.
Arch Linux Alacritty
Hi, I'm trying to assign some custom keybinds in
~/.config/nushell/config.nu
and it seems that thetab
keycode plus a modifier doesn't work.I already disabled all
tab
keybindings to test just the keybinding with the modifier. I also tried the same keybind with the same modifier but with another keycode and this works. It's like the modifier key doesn't work with the tab key code .Steps to reproduce
Screenshots
The keybind I tried to achieve