-
I'm running nightly build of wezterm on Arch Linux.
Normally in other terminals, I use |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 6 replies
-
When debugging key sequences there are two levels of thing to look at:
I'll look into resolving this, but for now you can workaround this by defining a key mapping: local wezterm = require 'wezterm';
return {
keys = {
{key="/", mods="CTRL", action=wezterm.action{SendString="\x1f"}},
}
} |
Beta Was this translation helpful? Give feedback.
-
To help with the debugging, what keyboard layout are you using? |
Beta Was this translation helpful? Give feedback.
When debugging key sequences there are two levels of thing to look at:
wezterm --config debug_key_events=true
and it will log its interpretation of the keys that are being pressed. Under X11, we log:key_event KeyEvent { key: Char('/'), modifiers: CTRL, raw_key: None, raw_modifiers: CTRL, raw_code: Some(61), repeat_count: 1, key_is_down: true }
which shows that it is being recognized correctlyod -c
and then type the key sequence to see how it is being encoded to send to the application:^O
^_
I'll look into resolving this, but for now you can workaround this by defining a key mapping: