Skip to content

ctrl-J gets reported as KeyCR on some terminals #911

@stefanhaller

Description

@stefanhaller

I'm in the process of updating lazygit to use tcell v2.13.4 (not v3 yet, this will come next).

There's a regression with handling ctrl-J on macOS Terminal (version 2.14, I'm on macOS 15.7.3) and on VS Code's built-in terminal: pressing ctrl-J gets reported as KeyCR, not KeyCtrlJ as it used to. My suspicion is that these don't support the CSI-u protocol, but I haven't verified that.

Other terminals report it correctly as KeyCtrlJ (ghostty, WezTerm, iTerm2).

That's a show-stopper for adoption of the new version for us, as ctrl-J is a frequently used keybinding in lazygit.

EDIT: tested it with v3 too now (v3.0.3), same problem there.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions