starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 16:05:21 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Two styles of delimiter for ANSI control codes #20059

New Issue
Closed
opened 2026-01-31 07:02:10 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 07:02:10 +00:00
Owner
Copy Link

Originally created by @the-moog on GitHub (Jun 9, 2023).

Windows Terminal version

1.16.10261.0

Windows build number

10.0.19045.0

Other Software

Stock Ubuntu/WSL 23.04

Steps to reproduce

I believe other terminals allow : or semicolon ; as field separators. I tried that with WT and found it to be inconsistent.
Here is a link to a script that tries various colours, you can run it with a delimiter as a parameter to demonstrate this.
https://gist.github.com/the-moog/0a6281dd284749331516dbfceb3fe5c0

Here is a link where somebody has tried to collate the relevant compliance of various terminals.
https://github.com/termstandard/colors

Expected Behavior

Either form works

Actual Behavior

Only ; is consistent

Originally created by @the-moog on GitHub (Jun 9, 2023). ### Windows Terminal version 1.16.10261.0 ### Windows build number 10.0.19045.0 ### Other Software Stock Ubuntu/WSL 23.04 ### Steps to reproduce I believe other terminals allow `:` or semicolon `;` as field separators. I tried that with WT and found it to be inconsistent. Here is a link to a script that tries various colours, you can run it with a delimiter as a parameter to demonstrate this. [https://gist.github.com/the-moog/0a6281dd284749331516dbfceb3fe5c0](https://gist.github.com/the-moog/0a6281dd284749331516dbfceb3fe5c0 ) Here is a link where somebody has tried to collate the relevant compliance of various terminals. [https://github.com/termstandard/colors](https://github.com/termstandard/colors) ### Expected Behavior Either form works ### Actual Behavior Only ; is consistent
claunia added the Issue-TaskArea-VTResolution-Duplicate labels 2026-01-31 07:02:11 +00:00
claunia commented 2026-01-31 07:02:12 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jun 9, 2023):

Reading through the linked xterm issues and their reasoning about why : should be supported for these color sequences made a lot of sense to me. The tl;dr is that ; should delimit parameters that can exist in any arbitrary order, but the parameters in a color sequence like 38;5;n cannot be reordered and so 38:5:n or 38:2:r:g:b should've technically been used from the start. This was apparently even a concern when these sequences were first introduced in the 90s (here).

I'm all in favor of making such a compatibility change, especially given that xterm/libvte and many of the other most popular terminals accept it.

@lhecker commented on GitHub (Jun 9, 2023): Reading through the linked xterm issues and their reasoning about why `:` should be supported for these color sequences made a lot of sense to me. The tl;dr is that `;` should delimit parameters that can exist in any arbitrary order, but the parameters in a color sequence like `38;5;n` cannot be reordered and so `38:5:n` or `38:2:r:g:b` should've technically been used from the start. This was apparently even a concern when these sequences were first introduced in the 90s ([here](https://bugzilla.gnome.org/show_bug.cgi?id=685759)). I'm all in favor of making such a compatibility change, especially given that xterm/libvte and many of the other most popular terminals accept it.
claunia commented 2026-01-31 07:02:12 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 9, 2023):

Pretty sure this is already tracked in #4321

@zadjii-msft commented on GitHub (Jun 9, 2023): Pretty sure this is already tracked in #4321
claunia commented 2026-01-31 07:02:12 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 9, 2023):

Absolutely is! Thanks Mike!

/dup #4321

@DHowett commented on GitHub (Jun 9, 2023): Absolutely is! Thanks Mike! /dup #4321
claunia commented 2026-01-31 07:02:12 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Jun 9, 2023):

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!

@microsoft-github-policy-service[bot] commented on GitHub (Jun 9, 2023): 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 Area-VT Issue-Task 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#20059
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?