`disable_default_key_bindings` does not affect some of the behaviors of Ctrl+C (keybinding appears to be hardcoded)

[crabdancing]

`disable_default_key_bindings` does not affect some of the behaviors of Ctrl+C (keybinding appears to be hardcoded)

[crabdancing]

{ key = 'q', mods = 'CTRL', action = act.Multiple { act.ScrollToBottom, act.SendKey { key = 'q', mods = 'CTRL' } } } worked, thanks! :)

[bew]

This behavior is not specific to Ctrl-c, all keys will scroll to the end.
Try to set scroll_to_bottom_on_input = false, although it won't scroll it will still send those keys but you won't see them
ref: https://wezfurlong.org/wezterm/config/lua/config/scroll_to_bottom_on_input.html

(note: with nu you can also do seq 1 100 to quickly write some output 🙃)

[crabdancing]

@bew

Woah! But Ctrl+Shift+C doesn't do it. I guess it's special behavior of the shift key, then? I should look at the code for input processing.

Also, I didn't know nushell had seq like Bash & Fish do. Thanks for the tip :D

Edit: looks like it works. Now all I'd like to do is get the scrolling behavior back, but for Ctrl+Q specifically. Maybe I can rig it up with some Lua?

[bew]

Yeah, I think using wezterm.action.ScrollToBottom should do it?
Ref: https://wezfurlong.org/wezterm/config/lua/keyassignment/ScrollToBottom.html

[crabdancing]

Oh, awesome! Is there a way of binding some code to a keybinding without intercepting the keybinding? When I do { key = 'q', mods = 'CTRL', action = act.ScrollToBottom }, it eats Ctrl+Q and the terminal stack can't respond to the keypress.

[bew]

Well the simplest solution here would be to use a act.Multiple action, to call act.ScrollToBottom then act.SendKey with the key you want to send.

Check these additional docs:

• https://wezfurlong.org/wezterm/config/lua/keyassignment/Multiple.html
• https://wezfurlong.org/wezterm/config/lua/keyassignment/SendKey.html

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.