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

ANSISYSRC / DECRC reset color attributes #19154

New Issue
Closed
opened 2026-01-31 06:35:17 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 06:35:17 +00:00
Owner
Copy Link

Originally created by @alabuzhev on GitHub (Dec 28, 2022).

Windows Terminal version

WT 1.16.3463.0, OpenConsole 1.16.2212.12003

Windows build number

10.0.19045.2364

Other Software

No response

Steps to reproduce

https://learn.microsoft.com/en-us/windows/console/console-virtual-terminal-sequences#simple-cursor-positioning

Sequence Shorthand Behavior
ESC 7 DECSC Save Cursor Position in Memory**
ESC 8 DECSR Restore Cursor Position from Memory**

https://learn.microsoft.com/en-us/windows/console/console-virtual-terminal-sequences#cursor-positioning

<html>
Sequence Code Description Behavior
ESC [ s ANSISYSSC Save Cursor – Ansi.sys emulation **With no parameters, performs a save cursor operation like DECSC
ESC [ u ANSISYSRC Restore Cursor – Ansi.sys emulation **With no parameters, performs a restore cursor operation like DECRC

Unpack and run the cmd file in WT and OpenConsole:
test_cusror_position.zip

It sets color attributes and draws a few lines, saving and restoring cursor position along the way.

Expected Behavior

Since DECRC & ANSISYSRC restore cursor position only (according to the documentation above), I expect the color attributes to be applied to all the printed text.

It works as expected in conhost.exe 10.0.19041.1566 that comes with the OS:

image

Actual Behavior

Color attributes are reset.

OpenConsole 1.16.2212.12003:
image

WT 1.16.3463.0:
image

Originally created by @alabuzhev on GitHub (Dec 28, 2022). ### Windows Terminal version WT 1.16.3463.0, OpenConsole 1.16.2212.12003 ### Windows build number 10.0.19045.2364 ### Other Software _No response_ ### Steps to reproduce https://learn.microsoft.com/en-us/windows/console/console-virtual-terminal-sequences#simple-cursor-positioning Sequence | Shorthand | Behavior -- | -- | -- ESC 7 | DECSC | Save Cursor Position in Memory** ESC 8 | DECSR | Restore Cursor Position from Memory** https://learn.microsoft.com/en-us/windows/console/console-virtual-terminal-sequences#cursor-positioning <html> <body> <!--StartFragment--> Sequence | Code | Description | Behavior -- | -- | -- | -- ESC [ s | ANSISYSSC | Save Cursor – Ansi.sys emulation | **With no parameters, performs a save cursor operation like DECSC ESC [ u | ANSISYSRC | Restore Cursor – Ansi.sys emulation | **With no parameters, performs a restore cursor operation like DECRC Unpack and run the cmd file in WT and OpenConsole: [test_cusror_position.zip](https://github.com/microsoft/terminal/files/10316390/test_cusror_position.zip) It sets color attributes and draws a few lines, saving and restoring cursor position along the way. ### Expected Behavior Since DECRC & ANSISYSRC restore cursor position *only* (according to the documentation above), I expect the color attributes to be applied to *all the printed text*. It works as expected in conhost.exe 10.0.19041.1566 that comes with the OS: ![image](https://user-images.githubusercontent.com/11453922/209871450-eed9b6bd-b854-464b-b6d1-b753fb472f1f.png) ### Actual Behavior Color attributes are reset. OpenConsole 1.16.2212.12003: ![image](https://user-images.githubusercontent.com/11453922/209871612-339ade2d-52f9-4da8-ae08-2f4ac95d4f80.png) WT 1.16.3463.0: ![image](https://user-images.githubusercontent.com/11453922/209871951-04168e52-2155-4ee9-ba0c-ea7976625843.png)
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 06:35:17 +00:00
claunia commented 2026-01-31 06:35:18 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Dec 29, 2022):

Honestly our documentation on VT sequences is not great. You should really refer to the DEC manuals for any DEC sequences, or the XTerm documentation for most of the non-standard stuff.

And quoting the DEC documentation, DECSC is meant to work as follows:

Saves the following items in the terminal’s memory:
• Cursor position
• Character attributes set by the SGR command
• Character sets (G0, G1, G2, or G3) currently in GL and GR
• Wrap flag (autowrap or no autowrap)
• State of origin mode (DECOM)
• Selective erase attribute
• Any single shift 2 (SS2) or single shift 3 (SS3) functions sent

And most modern terminals essentially treat the ANSISC and ANSIRCsequences as aliases for DECSC and DECRC (XTerm certainly does), so that's why we do that.

I would love one day for us to have a compatibility mode for something like ANSI.SYS and/or ANSI-BBS, but that's not likely to happen anytime soon, and I suspect that's not really what you want anyway.

And the reason it "works" for you in conhost is because that was originally a bug that got fixed a few years back, and it often take years for OpenConsole fixes to make it into the inbox conhost. So I suspect you're only likely to see the correct behavior in a Windows 11 release.

@j4james commented on GitHub (Dec 29, 2022): Honestly our documentation on VT sequences is not great. You should really refer to the DEC manuals for any DEC sequences, or the XTerm documentation for most of the non-standard stuff. And quoting the DEC documentation, `DECSC` is meant to work as follows: > Saves the following items in the terminal’s memory: > • Cursor position > • Character attributes set by the SGR command > • Character sets (G0, G1, G2, or G3) currently in GL and GR > • Wrap flag (autowrap or no autowrap) > • State of origin mode (DECOM) > • Selective erase attribute > • Any single shift 2 (SS2) or single shift 3 (SS3) functions sent And most modern terminals essentially treat the `ANSISC` and `ANSIRC`sequences as aliases for `DECSC` and `DECRC` (XTerm certainly does), so that's why we do that. I would love one day for us to have a compatibility mode for something like ANSI.SYS and/or ANSI-BBS, but that's not likely to happen anytime soon, and I suspect that's not really what you want anyway. And the reason it "works" for you in conhost is because that was originally a bug that got fixed a few years back, and it often take years for OpenConsole fixes to make it into the inbox conhost. So I suspect you're only likely to see the correct behavior in a Windows 11 release.
claunia commented 2026-01-31 06:35:21 +00:00
Author
Owner
Copy Link

@alabuzhev commented on GitHub (Dec 29, 2022):

Honestly our documentation on VT sequences is not great

I see, thanks James. It's a bit strange that VT doesn't have a way to save & restore cursor position only, but... it's not the only strange thing about VT.

If it's a documentation issue, it would be nice to fix it and mention somewhere at that page that it is subject to change as VT support improves and one should check other sources to ensure compatibility - it can be frustrating to implement something according to the documentation, see it working in your dev environment and then discover that it only works due to a bug and will be broken in future releases.

@alabuzhev commented on GitHub (Dec 29, 2022): > Honestly our documentation on VT sequences is not great I see, thanks James. It's a bit strange that VT doesn't have a way to save & restore cursor position only, but... it's not the only strange thing about VT. If it's a documentation issue, it would be nice to fix it and mention somewhere at that page that it is subject to change as VT support improves and one should check other sources to ensure compatibility - it can be frustrating to implement something according to the documentation, see it working in your dev environment and then discover that it only works due to a bug and will be broken in future releases.
claunia commented 2026-01-31 06:35:21 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Dec 29, 2022):

If it's a documentation issue, it would be nice to fix it and mention somewhere at that page that it is subject to change as VT support improves and one should check other sources to ensure compatibility

I think that's a good idea. There's an existing issue in the documentation repo for the VT sequences page from 2019 (see https://github.com/MicrosoftDocs/Console-Docs/issues/91), and that doesn't seem likely to be addressed any time soon. But a small update that just directs people to other sources would be a significant improvement in my opinion, and that's the sort of PR that could be reasonably easy for a volunteer contributor to do (although it's probably best to wait to see what the core devs have to say on the subject).

@j4james commented on GitHub (Dec 29, 2022): > If it's a documentation issue, it would be nice to fix it and mention somewhere at that page that it is subject to change as VT support improves and one should check other sources to ensure compatibility I think that's a good idea. There's an existing issue in the documentation repo for the VT sequences page from 2019 (see https://github.com/MicrosoftDocs/Console-Docs/issues/91), and that doesn't seem likely to be addressed any time soon. But a small update that just directs people to other sources would be a significant improvement in my opinion, and that's the sort of PR that could be reasonably easy for a volunteer contributor to do (although it's probably best to wait to see what the core devs have to say on the subject).
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 Needs-Triage
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#19154
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?