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

OSC escape sequences received out-of-order in 3rd-party terminals #21762

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

Originally created by @acarl005 on GitHub (May 23, 2024).

Windows Terminal version

1.19.11213.0

Windows build number

10.0.22631.0

Other Software

No response

Steps to reproduce

ANSI compatibility has been pretty good in ConPTY. We're coming up on some niche cases.

In a 3rd-party terminal, e.g. alacritty, produce some text with an OSC escape sequence interleaved between some text.

PowerShell 7.4.2
PS> echo "hello `e]2;new title`a world"
hello  world

Visually, things look pretty OK. The correct text is echo'd and the title is changed.

Screenshot 2024-05-23 195707

But, here is the exact data that alacritty read out of ConPTY:


hello  world
PS> ESC]0;new titleBEL

Observe that when the text was produced in the shell, the OSC command to set title was between "hello" and "world". However, when the text was read out of ConPTY by the terminal, the ordering is changed.

Expected Behavior

I expect the ordering of text, including the ANSI escape sequences, to be preserved.

Actual Behavior

ANSI escape sequences are being parsed and re-serialized in a "lossy" way. While this may be necessary when a Windows Terminal is involved, it isn't when the terminal application only receives ANSI sequences. That is, there is no need to try to parse the ANSI. ConPTY does still need to convert console API calls coming from Windows command-line apps, but plain ANSI text doesn't need any conversion.

Originally created by @acarl005 on GitHub (May 23, 2024). ### Windows Terminal version 1.19.11213.0 ### Windows build number 10.0.22631.0 ### Other Software _No response_ ### Steps to reproduce ANSI compatibility has been pretty good in ConPTY. We're coming up on some niche cases. In a 3rd-party terminal, e.g. alacritty, produce some text with an OSC escape sequence _interleaved_ between some text. ``` PowerShell 7.4.2 PS> echo "hello `e]2;new title`a world" hello world ``` Visually, things look pretty OK. The correct text is echo'd and the title is changed. ![Screenshot 2024-05-23 195707](https://github.com/microsoft/terminal/assets/8334252/55ecf7a0-4559-474c-b9ed-a8625c4f0fd0) But, here is the exact data that alacritty read out of ConPTY: ``` hello world PS> ESC]0;new titleBEL ``` Observe that when the text was produced in the shell, the OSC command to set title was between "hello" and "world". However, when the text was read out of ConPTY by the terminal, the ordering is changed. ### Expected Behavior I expect the ordering of text, including the ANSI escape sequences, to be preserved. ### Actual Behavior ANSI escape sequences are being parsed and re-serialized in a "lossy" way. While this may be necessary when a Windows Terminal is involved, it isn't when the terminal application only receives ANSI sequences. That is, there is no need to try to parse the ANSI. ConPTY does still need to convert console API calls coming from Windows command-line apps, but plain ANSI text doesn't need any conversion.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 07:54:12 +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 Issue-Bug Resolution-Duplicate
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#21762
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?