Confusion regarding legal keys in keymap #837
|
Im trying to generate a keymap that plays well with Windows Terminal, but so far its a mixed bag. And it looks to me that some key-combinations are not loaded correctly. The things im trying to accomplish is 1: change/rotate focus of panel I am aware that some key-combinations are "swallowed" by the terminal so if some are known i would love that Tested on Platform Win11 I only using the default profile and used the KeyMapEditor to generate a keymap, and loaded it with Expectation: Being able to provide a combination of almost all keys in the KeyMapEditor and have tem perform the operations they are linked too. Actual behaviour: When trying to add some key combinations, only some hare registered in full. Trying to assigne It will show up correctly in the KeyMapEditor, but the in-app-key list shows it as For code_editor.next_buffer i have tried to assign This works in CMD, but not in Windows Terminal. And it shows as It seems to be universal for Any experience with Windows terminal and keypresses and any known limitaions with textual? |
Replies: 1 comment
|
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-modifiers Windows Terminal never recognizes |
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…