starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

A way to read (from a console) a mix of “bindable keypresses” and Unicode? #489

New Issue
Open
opened 2026-01-30 21:53:35 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 21:53:35 +00:00
Owner
Copy Link

Originally created by @ilyaza on GitHub (Dec 17, 2018).

[Given a dearth of documentation on robust handling of user character input on Windows, I do not know whether this is a feature request, or not. So I post it here.]

As far as I understand, there is no way for a console application to process a mix of input of “accelerators” keypresses (such as Ctrl-Shift-= etc) and of Unicode characters. The major stumbling block is the recognition of dead keys: the application cannot tell a dead key from an “accelerator”.

(Using the undocumented flag of ToUnicodeEx(), one could do it if one knew the current “input locale” — but I see no way to find the input locale due to the console wrapper running with very high elevation…)

Question 1: is the analysis above valid? Or maybe there is some clever trick to circumvent this?

Question 2: is there going to be changes in this regard, so that applications can recognize dead keys

Question 3: A way to see changes of the “input locale” would be also beneficial!

Originally created by @ilyaza on GitHub (Dec 17, 2018). [Given a dearth of documentation on robust handling of user character input on Windows, I do not know whether this is a feature request, or not. So I post it here.] As far as I understand, there is no way for a console application to process a mix of input of “accelerators” keypresses (such as <kbd>Ctrl</kbd>-<kbd>Shift</kbd>-<kbd>=</kbd> etc) and of Unicode characters. The major stumbling block is the recognition of dead keys: the application cannot tell a dead key from an “accelerator”. (Using the undocumented flag of `ToUnicodeEx()`, one could do it if one knew the current “input locale” — but I see no way to find the input locale due to the console wrapper running with very high elevation…) Question 1: is the analysis above valid? Or maybe there is some clever trick to circumvent this? Question 2: is there going to be changes in this regard, so that applications can recognize dead keys Question 3: A way to see changes of the “input locale” would be also beneficial!
claunia added the Product-ConhostIssue-QuestionArea-Input labels 2026-01-30 21:53:35 +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 Area-Input Issue-Question Product-Conhost
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#489
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?