starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Unexpected ANSI sequence behavior in cmd.exe #17639

New Issue
Closed
opened 2026-01-31 05:48:38 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 05:48:38 +00:00
Owner
Copy Link

Originally created by @Zeek05 on GitHub (Jun 5, 2022).

Windows Terminal version

No response

Windows build number

Microsoft Windows [Version 10.0.22000.675]

Other Software

cmd.exe

Steps to reproduce

Apply any SGR sequence that affects character attributes in cmd.

Expected Behavior

IMG_9665

LEFT: You can see that the ANSI escape sequences in Windows Terminal are working as intended.

Actual Behavior

RIGHT: These changes are not propagating to CMD.exe, resizing the screen creates this bleeding effect.

This issue is related to #32

Originally created by @Zeek05 on GitHub (Jun 5, 2022). ### Windows Terminal version _No response_ ### Windows build number Microsoft Windows [Version 10.0.22000.675] ### Other Software cmd.exe ### Steps to reproduce Apply any SGR sequence that affects character attributes in cmd. ### Expected Behavior ![IMG_9665](https://user-images.githubusercontent.com/61340927/172073492-c08616b5-00cb-41bd-a573-899bc12ea869.png) **LEFT:** You can see that the ANSI escape sequences in Windows Terminal are working as intended. ### Actual Behavior **RIGHT**: These changes are not propagating to CMD.exe, resizing the screen creates this bleeding effect. This issue is related to #32
claunia added the Issue-BugResolution-DuplicateProduct-Terminal labels 2026-01-31 05:48:39 +00:00
claunia commented 2026-01-31 05:48:39 +00:00
Author
Owner
Copy Link

@Zeek05 commented on GitHub (Jun 5, 2022):

I had contacted MS support for this issue and they redirected me to this GitHub. I am not sure how this is relevant to Terminal but, I am using cmd.exe and this place seems the most relevant.

Edit: Why is the image so compressed? 😂

@Zeek05 commented on GitHub (Jun 5, 2022): I had contacted MS support for this issue and they redirected me to this GitHub. I am not sure how this is relevant to Terminal but, I am using cmd.exe and this place seems the most relevant. Edit: Why is the image so compressed? 😂
claunia commented 2026-01-31 05:48:40 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 6, 2022):

I am not sure how this is relevant to Terminal

Good news! The code for Windows Terminal and the legacy console window are both here in this repository.

I bet you're seeing an issue we've since fixed, where attributes get extended across the screen when the window is resized. That was #32, and it applied to any text styling (color, underline, hyperlink, ...)

What is tat?

@DHowett commented on GitHub (Jun 6, 2022): > I am not sure how this is relevant to Terminal Good news! The code for Windows Terminal *and* the legacy console window are both here in this repository. I bet you're seeing an issue we've since fixed, where attributes get extended across the screen when the window is resized. That was #32, and it applied to any text styling (color, underline, hyperlink, ...) What is `tat`?
claunia commented 2026-01-31 05:48:40 +00:00
Author
Owner
Copy Link

@Zeek05 commented on GitHub (Jun 6, 2022):

I am not sure how this is relevant to Terminal

Good news! The code for Windows Terminal and the legacy console window are both here in this repository.

I bet you're seeing an issue we've since fixed, where attributes get extended across the screen when the window is resized. That was #32, and it applied to any text styling (color, underline, hyperlink, ...)

What is tat?

tat is an application I am developing.

Shortest explanation is, it simply sends the escape sequences to STDOUT.
So, when I do tat underline it's just emitting the underline escape sequence to stdout

I have the latest version of windows and conhost, I am not sure why the bug is persisting then? This was a screenshot yesterday..

Specifically for underlining, the program does the following:
printf("\x1b[4m");

On Windows Terminal, it works just as expected. However on conhost it is not.

@Zeek05 commented on GitHub (Jun 6, 2022): > > I am not sure how this is relevant to Terminal > > Good news! The code for Windows Terminal _and_ the legacy console window are both here in this repository. > > I bet you're seeing an issue we've since fixed, where attributes get extended across the screen when the window is resized. That was #32, and it applied to any text styling (color, underline, hyperlink, ...) > > What is `tat`? tat is an application I am developing. Shortest explanation is, it simply sends the escape sequences to STDOUT. So, when I do `tat underline` it's just emitting the underline escape sequence to stdout I have the latest version of windows and conhost, I am not sure why the bug is persisting then? This was a screenshot yesterday.. Specifically for underlining, the program does the following: ` printf("\x1b[4m");` On Windows Terminal, it works just as expected. However on conhost it is not.
claunia commented 2026-01-31 05:48:40 +00:00
Author
Owner
Copy Link

@237dmitry commented on GitHub (Jun 6, 2022):

Resizing terminal window works as %esc%[0m

Screenshot 2022-06-06 130742

@237dmitry commented on GitHub (Jun 6, 2022): Resizing terminal window works as `%esc%[0m` ![Screenshot 2022-06-06 130742](https://user-images.githubusercontent.com/78153320/172141005-54be4a3d-39ec-4c7b-a33c-22fff6fb79b8.png)
claunia commented 2026-01-31 05:48:40 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 6, 2022):

Yea, this looks like a combo of #32 with {that one issue where we were initializing the buffer with the current attributes, not the default ones}. I'd reckon that the conhost changes to fix #32 aren't in 10.0.22000.675, but should be available in the next major Win11 release. (I don't know what that build number will be yet).

/dup #32

@zadjii-msft commented on GitHub (Jun 6, 2022): Yea, this looks like a combo of #32 with {that one issue where we were initializing the buffer with the current attributes, not the default ones}. I'd reckon that the conhost changes to fix #32 aren't in 10.0.22000.675, but should be available in the next major Win11 release. (I don't know what that build number will be yet). /dup #32
claunia commented 2026-01-31 05:48:40 +00:00
Author
Owner
Copy Link

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

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jun 6, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 Product-Terminal 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#17639
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?