Some configs do not work

[python128]

I am not able to allow certain keymaps to work.
Here is my config.toml

theme = "bogster"

[lsp]
display-messages = true

[keys.normal]
S-left = "extend_char_left"
S-right = "extend_char_right"
S-up = "extend_line_up"
S-down = "extend_line_down"

"#" = "toggle_comments"
C-c = "no_op"
q = { q = "wclose" }
"space" = { "space" = "keep_primary_selection" }

A-o = "add_newline_below"
A-O = [ "open_above", "normal_mode" ]

[keys.insert]
C-backspace = "delete_word_backward"

• Here, C-O and C-backspace doesn't work.
• I have tried C-O with add_newline_above and the given config both.
• A-o seems to work perfectly fine.

Environment

• Platform: Linux(WSL)
• Helix version: v0.5.0-94-gd3def16 (from git describe)

Link to gif.

[LollipopFt]

just a suggestion (it may not work) but i think special keys like left and right should be enclosed in "?

[LollipopFt]

see here, the entire command is encapsulated in double quotes.

[Omnikar]

just a suggestion (it may not work) but i think special keys like left and right should be enclosed in "?

Quotes are only required by special TOML characters like ., #, {, etc.

[sudormrfbin]

C-backspace doesn't work

Backspace with modifiers have been problematic for terminal emulators to handle in general (some represent it as control+h, some send different keycodes, etc). There's also an open ticket in the crossterm repo: crossterm-rs/crossterm#504.

[pickfire]

Yeah, some keys are special, for example C-i is tab so I think only one of them works. We didn't do any post-processing to solve this ambiguity issue in helix.

[python128]

Is A-O also an ambiguous key?
If so, why does it work in Kak? (Is it because it is not crossterm or something related?)

[David-Else]

Hi, the C-backspace = "delete_word_backward" not working is killing my typing. I think it is very important for touch typing to be able to easily delete the last word in insert mode, it is nearly always better to delete the misspelled word entirely and start again for the sake of muscle memory. ctrl-backspace is the standard in most software (for example, right here in editing this message on github it works)

In Gnome I set my backspace to be caps lock:

    gsettings set org.gnome.desktop.input-sources \
        xkb-options "['caps:backspace', 'terminate:ctrl_alt_bksp']"

and in my .bashrc i set ctrl-backspace to delete the previous word:

stty werase \^H # set ctrl-backspace to delete previous word instead of ctrl-w

Now in the terminal (kitty and gnome terminal) and Neovim I can delete the previous word with ctrl+caps-lock.

Is it correct that this is never going to work until crossterm-rs/crossterm#504 is fixed? :(

[sudormrfbin]

It might be solved if/when we migrate from crossterm to termwiz, in the meantime you could use ctrl-w in insert mode for the same purpose (carried over from vim).

[the-mikedavis]

With the update to crossterm 0.25 in #3390, it looks like there are a lot of key combinations that were mistranslated that have been fixed such as C-backspace and C-m. I can see these being translated correctly on Kitty now but I'm not sure if the fixes apply to all terminal emulators.

[groves]

Kitty, foot, and WezTerm support it according to this crossterm comment.