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 #13981] [MERGED] Add support for DECARM (Auto Repeat Mode) #29867

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

📋 Pull Request Information

Original PR: https://github.com/microsoft/terminal/pull/13981
Author: @j4james
Created: 9/13/2022
Status: ✅ Merged
Merged: 10/11/2022
Merged by: @carlos-zamora

Base: main ← Head: feature-decarm

📝 Commits (2)

  • 0871479 Add support for auto repeat mode.
  • 619e6a0 Add unit test for auto repeat mode.

📊 Changes

5 files changed (+80 additions, -1 deletions)

View changed files

📝 src/terminal/adapter/DispatchTypes.hpp (+1 -0)
📝 src/terminal/adapter/adaptDispatch.cpp (+6 -0)
📝 src/terminal/adapter/ut_adapter/inputTest.cpp (+54 -0)
📝 src/terminal/input/terminalInput.cpp (+15 -0)
📝 src/terminal/input/terminalInput.hpp (+4 -1)

📄 Description

This PR adds support for the DECARM (Auto Repeat Mode) sequence, which
controls whether a keypress automatically repeats if you keep it held
down for long enough.

Note that this won't fully work in Windows Terminal until issue #8440 is
resolved.

Every time we receive a KeyDown event, we record the virtual key code
to track that as the last key pressed. If we receive a KeyUp event the
matches that last key code, we reset that field. Then if the Auto Repeat
Mode is reset, and we receive a KeyDown event that matches the last
key code, we simply ignore it.

Validation Steps Performed

I've manually tested the DECARM functionality in Vttest and confirmed
that it's working as expected. Although note that in Windows Terminal
this only applies to non-alphanumeric keys for now (e.g. Tab, BackSpace,
arrow keys, etc.)

I've also added a basic unit test that verifies that repeated key
presses are suppressed when the DECARM mode is disabled.

Closes #13919

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/microsoft/terminal/pull/13981 **Author:** [@j4james](https://github.com/j4james) **Created:** 9/13/2022 **Status:** ✅ Merged **Merged:** 10/11/2022 **Merged by:** [@carlos-zamora](https://github.com/carlos-zamora) **Base:** `main` ← **Head:** `feature-decarm` --- ### 📝 Commits (2) - [`0871479`](https://github.com/microsoft/terminal/commit/087147947df43e8c32049537d9b0ca837a1b34d6) Add support for auto repeat mode. - [`619e6a0`](https://github.com/microsoft/terminal/commit/619e6a098cffc6efdedd601ae2afb5f533d23485) Add unit test for auto repeat mode. ### 📊 Changes **5 files changed** (+80 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/terminal/adapter/DispatchTypes.hpp` (+1 -0) 📝 `src/terminal/adapter/adaptDispatch.cpp` (+6 -0) 📝 `src/terminal/adapter/ut_adapter/inputTest.cpp` (+54 -0) 📝 `src/terminal/input/terminalInput.cpp` (+15 -0) 📝 `src/terminal/input/terminalInput.hpp` (+4 -1) </details> ### 📄 Description This PR adds support for the `DECARM` (Auto Repeat Mode) sequence, which controls whether a keypress automatically repeats if you keep it held down for long enough. Note that this won't fully work in Windows Terminal until issue #8440 is resolved. Every time we receive a `KeyDown` event, we record the virtual key code to track that as the last key pressed. If we receive a `KeyUp` event the matches that last key code, we reset that field. Then if the Auto Repeat Mode is reset, and we receive a `KeyDown` event that matches the last key code, we simply ignore it. ## Validation Steps Performed I've manually tested the `DECARM` functionality in Vttest and confirmed that it's working as expected. Although note that in Windows Terminal this only applies to non-alphanumeric keys for now (e.g. Tab, BackSpace, arrow keys, etc.) I've also added a basic unit test that verifies that repeated key presses are suppressed when the `DECARM` mode is disabled. Closes #13919 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
claunia added the pull-request label 2026-01-31 09:37:20 +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#29867
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?