Skip to content
Discussion options

You must be logged in to vote

If the keys app (the keymap editor) doesn't detect a keypress, or if it gets it "wrong", then Harlequin will, too. That was kind of the point of the keys app -- sometimes it's not intuitive how your terminal forwards keypresses to the shell. In other words, your terminal is intercepting key presses and not passing them through as-is to your shell. There is nothing Harlequin can do about this.

In Winterm, this is configurable, sometimes, for some keypresses. See https://harlequin.sh/docs/troubleshooting/key-bindings and https://learn.microsoft.com/en-us/windows/terminal/customize-settings/actions and https://learn.microsoft.com/en-us/windows/terminal/customize-settings/actions#accepted-mod…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by tconbeer
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #826 on September 12, 2025 18:17.