Skip to content
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

input: legacy encoding falls back to mapping of logical key for ctrlseq #4528

Merged
merged 1 commit into from
Jan 3, 2025

Conversation

mitchellh
Copy link
Contributor

Fixes #4518

If our UTF8 encoding is not recognized, we fall back to the ASCII mapping of the logical key for the control sequence. This allows cyrillic control characters to work.

I also verified that non-cyrllic (US) and alternate layouts (Dvorak) work as expected still.

Fixes #4518

If our UTF8 encoding is not recognized, we fall back to the ASCII
mapping of the logical key for the control sequence. This allows
cyrillic control characters to work.

I also verified that non-cyrllic (US) and alternate layouts (Dvorak)
work as expected still.
@mitchellh mitchellh enabled auto-merge January 3, 2025 18:57
@mitchellh mitchellh merged commit ab9b142 into main Jan 3, 2025
48 checks passed
@mitchellh mitchellh deleted the push-nzrxskosttkx branch January 3, 2025 19:09
@github-actions github-actions bot added this to the 1.0.2 milestone Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

macOS: Russian ctrl+c generates incorrect encoding in normal mode
1 participant