-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent keybindings behavior for Alt Shift Combinations #3305
Comments
Yeah, on Unix it is This is one of many unfortunate consequences of all the legacy crap that Unix terminals have and the lack of standardization between them, as well as the lack of standardization between Unix and Windows terminals. |
Yeah, right now I have 2 versions of keybindings (1 with Shift 1 without) that binds to the same action as a workaround so that I can use the same json for both Linux and Windows. I will create a PR to fix this. |
@JoeKar This is less important than #3304 (but slightly inconvenient) so I am not too fussed about getting this sorted quickly. But my question would be should tcell be producing consistent output for this as well, considering tcell is just spitting out whatever it receives and this count as the quirks with linux vs windows. |
I assume that this is related to |
Description of the problem or steps to reproduce
When using the same keybindings on Windows and Linux, one works and the other does not.
Given there are two keybindings that are the same but displayed differently
Alt-Shift-E
Alt-E
The first one works on Windows but not on Linux, vice versa for the second one.
I tried both by pointing it to empty config directory using
micro -config-dir ./tmp
and modifying the keybindings thereWhen running
raw
, I can see indeed it is capturing different thingsOn Linux
On Windows
Specifications
Commit hash: 1f51d0b (Windows) 9176508 (Linux)
OS: Windows 11 and Arch Linux
Terminal: WezTerm
The text was updated successfully, but these errors were encountered: