starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-09 02:26:45 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Please finish support for OSC 4 and friends #464

New Issue
Open
opened 2026-01-30 21:52:57 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 21:52:57 +00:00
Owner
Copy Link

Originally created by @Jaykul on GitHub (Dec 6, 2018).

Originally assigned to: @zadjii-msft on GitHub.

I was really happy to see support for OSC 4 to set the 16 palette colors (and I recently helped a friend add it to the docs, the way it is now) ...

However, I have some problems. I'm hoping you can address them all as one request, but I'm happy to split them out. First, as background the xterm control sequences docs. Obviously these are not sacred, but they do represent a sort-of standard in that other terminals and tmux have implemented these same sequences the same way...

  1. OSC 4 should support multiple colors. XTerm and tmux (and others) support multiple pairs of index;spec without having to repeat the ESC]4; part, so you can do: ESC]4;0;rgb:00/00/00;1;rgb:00/00/70;...\\ and list out the whole set of colors as one giant escape sequence.
  2. It doesn't allow setting the extended xterm 88 or 256 color palette (see #313).
  3. It doesn't support querying. I should be able to put a "?" in place of the rgb spec and get back a control sequence (which is supposed to be the exact same format), such that it could be used to set the color to the same RGB value it is already. This would allow me to check if I'm dealing with PowerShell blue instead of magenta by writing ESC]4;5;?\\ and parsing the output

Additionally ... without support for OSC 10 and 11 I cannot change the default foreground and background colors, so there's no way to fix (even temporarily) the fact that PowerShell is using 5 as it's default background color. NOTE that these should also support querying with a "?"

AND EVEN WORSE ...

We really also need support for OSC 104 (and 110 and 111) which would reset the colors changed by OSC 4, 10, and 11 to their defaults. Note that if done right, they support resetting individual colors, but as a first draft, I'd settle for the parameterless reset of the entire table -- and for my own purposes, if you implement 110 and 111 as meaning force WHITE text on a BLACK background, without implementing 10 and 11, I wouldn't cry 😉

Originally created by @Jaykul on GitHub (Dec 6, 2018). Originally assigned to: @zadjii-msft on GitHub. I was really happy to see support for OSC 4 to **set** the 16 palette colors (and I recently helped a friend add it to the docs, _the way it is now_) ... However, I have some problems. I'm hoping you can address them all as one request, but I'm happy to split them out. First, as background the [xterm control sequences docs](http://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h2-Operating-System-Commands). Obviously these are not sacred, but they _do_ represent a sort-of standard in that _other_ terminals and tmux have implemented these same sequences the same way... 1. OSC 4 should support multiple colors. XTerm and tmux (and others) support multiple _pairs_ of `index;spec` without having to repeat the `ESC]4;` part, so you can do: `ESC]4;0;rgb:00/00/00;1;rgb:00/00/70;...\\` and list out the whole set of colors as one giant escape sequence. 2. It doesn't allow setting the extended xterm 88 or 256 color palette (see #313). 3. It doesn't support querying. I should be able to put a "?" in place of the rgb spec and get back a control sequence (which is supposed to be the exact same format), such that it could be used to set the color to the same RGB value it is already. This would allow me to _check_ if I'm dealing with PowerShell blue instead of magenta by writing `ESC]4;5;?\\` and parsing the output Additionally ... without support for OSC 10 and 11 I cannot change the default foreground and background colors, so there's no way to _fix_ (even temporarily) the fact that PowerShell is using 5 as it's default background color. NOTE that these should _also_ support querying with a "?" ## AND EVEN WORSE ... We really also need support for OSC 104 (and 110 and 111) which would **reset** the colors changed by OSC 4, 10, and 11 to their defaults. Note that if done right, they support resetting individual colors, but as a first draft, I'd settle for the parameterless reset of the entire table -- and for my own purposes, if you implement 110 and 111 as meaning force WHITE text on a BLACK background, _without_ implementing 10 and 11, I wouldn't cry 😉
claunia added the Issue-FeatureProduct-ConhostResolution-Fix-AvailableArea-VT labels 2026-01-30 21:52:57 +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 Area-VT Issue-Feature Product-Conhost Resolution-Fix-Available
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#464
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?