Kitty keyboard protocol, disambiguating key codes #5102
Replies: 4 comments
-
Got it working. I think this setting took precedence, because its default value is |
Beta Was this translation helpful? Give feedback.
-
Might also be worth adding an example to the docs, illustrating that you have to disable the other setting first. |
Beta Was this translation helpful? Give feedback.
-
The problem now is that esc is not being detected |
Beta Was this translation helpful? Give feedback.
-
After a restart it started working |
Beta Was this translation helpful? Give feedback.
-
I assume this option has to be turned in addition to enable_kitty_keyboard.
The key combo
ctrl-;
is being sent asesc
for me, withenable_kitty_keyboard = true
, which I have tested in neovim by trying the combo, as well as withshowkey -a
. I cannot test the native behavior of kitty to compare the two, because I don't have a linux machine, I'm on Windows 10 and using WSL forshowkey
and neovim.Doesn't
enable_kitty_keyboard = true
mean that things likectrl - shift - E
will be sent differently thanctrl - E
? For me they are sent the same. Does that mean the feature is disabled for me? Again, I can't test the native behavior, but it seems like it is.Is this feature in the latest build at all?
The point is to have things like
ctrl-i
andctrl-/
andctrl-.
andctrl-;
work for bindings in neovim, which I want to run through the terminal on wsl.Beta Was this translation helpful? Give feedback.
All reactions