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

Add support for passing DCS sequences over conpty #17625

New Issue
Closed
opened 2026-01-31 05:48:04 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 05:48:04 +00:00
Owner
Copy Link

Originally created by @j4james on GitHub (Jun 3, 2022).

Description of the new feature/enhancement

We don't currently support passing through DCS sequences over conpty, so they just get ignored. This hasn't been a significant issue up to now, because none of the existing DCS sequences could be meaningfully interpreted by the connected terminal. However, with the recent addition of the DECCTR sequence (for updating the color table), we now have a real use case for DCS passthrough.

Proposed technical implementation details (optional)

My plan was to add a helper function in AdaptDispatch that would create a "passthrough" string handler that DCS operations could choose to return when in conpty mode. This would start by flushing the renderer to make sure there wasn't any pending frame data, and also flushing the state machine to pass through the sequence introducer and parameters that had already been parsed. From then on, it would be the job of the returned string handler to forward the remaining sequence data via the state machine's ActionPassThroughString method.

By default I think we should still be ignoring DCS sequences that we don't understand. But if we know of a sequence that can meaningfully be interpreted by the terminal on the other end of the conpty pipe (like DECCTR), then we can choose to forward that using this passthrough handler.

Originally created by @j4james on GitHub (Jun 3, 2022). # Description of the new feature/enhancement We don't currently support passing through `DCS` sequences over conpty, so they just get ignored. This hasn't been a significant issue up to now, because none of the existing `DCS` sequences could be meaningfully interpreted by the connected terminal. However, with the recent addition of the `DECCTR` sequence (for updating the color table), we now have a real use case for `DCS` passthrough. # Proposed technical implementation details (optional) My plan was to add a helper function in `AdaptDispatch` that would create a "passthrough" string handler that `DCS` operations could choose to return when in conpty mode. This would start by flushing the renderer to make sure there wasn't any pending frame data, and also flushing the state machine to pass through the sequence introducer and parameters that had already been parsed. From then on, it would be the job of the returned string handler to forward the remaining sequence data via the state machine's `ActionPassThroughString` method. By default I think we should still be ignoring `DCS` sequences that we don't understand. But if we know of a sequence that can meaningfully be interpreted by the terminal on the other end of the conpty pipe (like `DECCTR`), then we can choose to forward that using this passthrough handler.
claunia added the Issue-FeatureNeeds-TriageResolution-Fix-CommittedNeeds-Tag-Fix labels 2026-01-31 05:48:05 +00:00
claunia commented 2026-01-31 05:48:05 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 6, 2022):

:tada:This issue was addressed in #13227, which has now been successfully released as Windows Terminal Preview v1.15.186.🎉

Handy links:

@ghost commented on GitHub (Jul 6, 2022): :tada:This issue was addressed in #13227, which has now been successfully released as `Windows Terminal Preview v1.15.186`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.15.186) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
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-Feature Needs-Tag-Fix Needs-Triage Resolution-Fix-Committed
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#17625
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?