starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

[PR #2836] Partially fix mapping of virtual keys to characters #25114

New Issue
Open
opened 2026-01-31 09:07:21 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 09:07:21 +00:00
Owner
Copy Link

Original Pull Request: https://github.com/microsoft/terminal/pull/2836

State: closed
Merged: Yes

Summary of the Pull Request

This PR mostly fixes the mapping of Alt combinations to unicode characters.

The case of AltGr was originally hotfixed by returning early in TerminalControl.
But this didn't fix e.g. AltShift combinations. See #2771 for instance.

This PR now fixes this particular remaining issue.
Cases where a single keypress generates more than a single UTF-16 code point (e.g. when diacritics come into play) are not fixed though, due to a limitation in the design of the low level KeyEvent class.

PR Checklist

Detailed Description of the Pull Request / Additional comments

This removes the special handling of AltGr in TerminalControl, so that terminalInput may now handle it by itself.

I believe it'd be nice to extend InputTest.cpp to include a test for the translation of Shift. to ">", but unfortunately this would be exclusive to US keyboard layouts.
My german keyboard layout for instance uses Shift< for this (there's a dedicated "<" key).
How would I build a unit test for this that works independent of "internationalization"?

Validation Steps Performed

  • Ensured that the expected behavior of #2771 can be observed.
  • The special handling of AltGr is being removed in this PR.
    -> Ensured that AltGr combinations still work.
**Original Pull Request:** https://github.com/microsoft/terminal/pull/2836 **State:** closed **Merged:** Yes --- ## Summary of the Pull Request This PR mostly fixes the mapping of <kbd>Alt</kbd> combinations to unicode characters. The case of <kbd>AltGr</kbd> was originally hotfixed by returning early in `TerminalControl`. But this didn't fix e.g. <kbd>Alt</kbd><kbd>Shift</kbd> combinations. See #2771 for instance. This PR now fixes this particular remaining issue. Cases where a single keypress generates more than a single UTF-16 code point (e.g. when diacritics come into play) are not fixed though, due to a limitation in the design of the low level `KeyEvent` class. ## PR Checklist * [x] Closes * Closes #2771 * Closes #1819 * Related #1694 (Not sure about that one - I don't understand the issue description) * [x] CLA signed. If not, go over [here](https://cla.opensource.microsoft.com/microsoft/Terminal) and sign the CLA * [ ] Tests added/passed * [x] Requires documentation to be updated * I changed the `ITerminalInput` interface * [ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #2771 ## Detailed Description of the Pull Request / Additional comments This removes the special handling of AltGr in `TerminalControl`, so that `terminalInput` may now handle it by itself. I believe it'd be nice to extend `InputTest.cpp` to include a test for the translation of <kbd>Shift</kbd><kbd>.</kbd> to ">", but unfortunately this would be exclusive to US keyboard layouts. My german keyboard layout for instance uses <kbd>Shift</kbd><kbd><</kbd> for this (there's a dedicated "<" key). How would I build a unit test for this that works independent of "internationalization"? ## Validation Steps Performed * Ensured that the expected behavior of #2771 can be observed. * The special handling of AltGr is being removed in this PR. -> Ensured that AltGr combinations still work.
claunia added the pull-request label 2026-01-31 09:07:21 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#25114
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?