claude-code - 💡(How to fix) Fix /terminal-setup falsely claims Shift+Enter is natively supported in WezTerm [1 comments, 2 participants]

TL;DR

To fix the issue, add a custom keybinding to WezTerm's configuration file wezterm.lua to correctly handle Shift+Enter.

Guidance

• Verify that the issue is specific to WezTerm's default keybinding for Shift+Enter, which sends a plain \r instead of a newline.
• Check the wezterm.lua configuration file for any existing keybindings that may be overriding the default behavior.
• Add the suggested keybinding to wezterm.lua to send the correct newline character: { key = "Enter", mods = "SHIFT", action = wezterm.action.SendString("\\x1b\\r") }.
• After adding the keybinding, restart WezTerm or reload the configuration to apply the changes.

Example

The provided code snippet in the issue can be used as a reference:

config.keys = {
  { key = "Enter", mods = "SHIFT", action = wezterm.action.SendString("\\x1b\\r") },
}

Add this to the wezterm.lua file to enable the correct Shift+Enter behavior.

Notes

This fix assumes that the issue is specific to WezTerm's default keybinding and that the wezterm.lua configuration file is being used. If using a different configuration file or setup, adjustments may be necessary.

Recommendation

Apply the workaround by adding the custom keybinding to wezterm.lua, as this provides a direct solution to the issue and allows for correct Shift+Enter behavior in WezTerm.