starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 08:24:54 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Pressing shift while a key is repeating terminates the repeat. Although this is consistent with Windows key event behavior, requesting a compatibility option #17796

New Issue
Closed
opened 2026-01-31 05:53:40 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 05:53:40 +00:00
Owner
Copy Link

Originally created by @unphased on GitHub (Jun 25, 2022).

Windows Terminal version

Windows Terminal Preview Version: 1.14.1451.0

Windows build number

Microsoft Windows NT 10.0.19044.0

Other Software

N/A

Steps to reproduce

  1. Hold down an alphanumeric key such as a. It begins to repeat.
  2. while holding that key down, depress a Shift key

Expected Behavior

To be consistent with behavior in macOS and Linux, the input from the alphanumeric key should continue: aaaaaaAAAA

Actual Behavior

Input stops when the Shift key comes down: aaaaaa

To get back the desired input one has to re-type the first key, and wait past the initial key repeat delay.

This is seen to be standard windows input event behavior, nevertheless, I would prefer to have independently generated key repeat events to replicate the behavior observed in the terminal on any other operating system.

Originally created by @unphased on GitHub (Jun 25, 2022). ### Windows Terminal version Windows Terminal Preview Version: 1.14.1451.0 ### Windows build number Microsoft Windows NT 10.0.19044.0 ### Other Software N/A ### Steps to reproduce 1. Hold down an alphanumeric key such as `a`. It begins to repeat. 2. while holding that key down, depress a Shift key ### Expected Behavior To be consistent with behavior in macOS and Linux, the input from the alphanumeric key should continue: `aaaaaaAAAA` ### Actual Behavior Input stops when the Shift key comes down: `aaaaaa` To get back the desired input one has to re-type the first key, *and* wait past the initial key repeat delay. This is seen to be standard windows input event behavior, nevertheless, I would prefer to have independently generated key repeat events to replicate the behavior observed in the terminal on any other operating system.
claunia added the Needs-TriageIssue-TaskNeeds-Tag-FixResolution-Won't-Fix labels 2026-01-31 05:53:40 +00:00
claunia commented 2026-01-31 05:53:42 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jun 27, 2022):

I can only speak for myself, but I don't think this is something we can easily implement. We don't generate those character input events - Windows does. Adding such a compatibility feature might be quite difficult to do correctly (with respect to Unicode, etc.) and not be worth the effort, considering that other Windows applications don't support this either.

@lhecker commented on GitHub (Jun 27, 2022): I can only speak for myself, but I don't think this is something we can easily implement. We don't generate those character input events - Windows does. Adding such a compatibility feature might be quite difficult to do correctly (with respect to Unicode, etc.) and not be worth the effort, considering that other Windows applications don't support this either.
claunia commented 2026-01-31 05:53:42 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 5, 2022):

Yea I'm inclined to agree here. If someone wants to correct me, I'm all ears, but I suspect it'll be quite a bit more than trivial to get repeated keypresses in this scenario. Sorry about that!

@zadjii-msft commented on GitHub (Jul 5, 2022): Yea I'm inclined to agree here. If someone wants to correct me, I'm all ears, but I suspect it'll be quite a bit more than trivial to get repeated keypresses in this scenario. Sorry about that!
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 Issue-Task Needs-Tag-Fix Needs-Triage Resolution-Won't-Fix
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#17796
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?