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

Unexpected behavior of ANSI 256 colors 0-7 and SGR 1? #21315

New Issue
Closed
opened 2026-01-31 07:39:58 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 07:39:58 +00:00
Owner
Copy Link

Originally created by @magus424 on GitHub (Feb 26, 2024).

Windows Terminal version

1.18.10301.0

Windows build number

10.0.22621.0

Other Software

No response

Steps to reproduce

Set "Intense text style" in the profile Appearance settings to "Bright colors"

Run echo -e '\e[0;34m 0;34m blue \e[0m\n\e[1;34m 1;34m high intensity blue \e[0m\n\e[38;5;4m 38;5;4m blue \e[0m\n\e[38;5;4m\e[1m 38;5;4m + 1m - high intensity blue? \e[0m\n\e[38;5;12m 38;5;12m bright blue \e[0m'

Expected Behavior

image
(image taken while in tmux 3.2a which somehow adjusts the behavior to match what I would expect, even if I change the "Intense text style" from bright to bold)

Actual Behavior

image
SGR1 is ignored, despite the color being in the basic 0-7 system range which I would expect to bump up to 8-15 given the "Bright colors" setting, similar to how 1;34m matches 94m with the bright setting.

On the other hand, if you flip the setting to "Bold font", the interaction works as I would expect:
image

Originally created by @magus424 on GitHub (Feb 26, 2024). ### Windows Terminal version 1.18.10301.0 ### Windows build number 10.0.22621.0 ### Other Software _No response_ ### Steps to reproduce Set "Intense text style" in the profile Appearance settings to "Bright colors" Run `echo -e '\e[0;34m 0;34m blue \e[0m\n\e[1;34m 1;34m high intensity blue \e[0m\n\e[38;5;4m 38;5;4m blue \e[0m\n\e[38;5;4m\e[1m 38;5;4m + 1m - high intensity blue? \e[0m\n\e[38;5;12m 38;5;12m bright blue \e[0m'` ### Expected Behavior ![image](https://github.com/microsoft/terminal/assets/384053/20fa8649-bfba-43a9-9f8e-b0b35534f7a2) (image taken while in tmux 3.2a which somehow adjusts the behavior to match what I would expect, even if I change the "Intense text style" from bright to bold) ### Actual Behavior ![image](https://github.com/microsoft/terminal/assets/384053/39e192e2-f3f1-4b97-9e94-c1d5fe59c6f7) SGR1 is ignored, despite the color being in the basic 0-7 system range which I would expect to bump up to 8-15 given the "Bright colors" setting, similar to how `1;34m` matches `94m` with the bright setting. On the other hand, if you flip the setting to "Bold font", the interaction works as I would expect: ![image](https://github.com/microsoft/terminal/assets/384053/44fe4250-80a0-4228-bc66-568b37ae4d77)
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 07:39:59 +00:00
claunia commented 2026-01-31 07:40:05 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 26, 2024):

Oh, I totally remember this one!

When we refined our support for the 256-color Xterm palette, we chose not to intensify those colors. Xterm treats them as being distinct, and so we follow their lead.

image

@DHowett commented on GitHub (Feb 26, 2024): Oh, I totally remember this one! When we refined our support for the 256-color Xterm palette, we chose _not_ to intensify those colors. Xterm treats them as being distinct, and so we follow their lead. ![image](https://github.com/microsoft/terminal/assets/189190/0310646a-f471-4feb-98ef-8c166cc626ea)
claunia commented 2026-01-31 07:40:10 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 26, 2024):

Thanks for the report! This was an intentional decision, based on how other terminal emulators work. I went and dug up some of our older discussions to give you more context. 😄

Here's the short version:

I'll tentatively close this one out as a /duplicate of #5384 😄

Stealing some notes from https://github.com/microsoft/terminal/issues/11507#issuecomment-943481690

@DHowett commented on GitHub (Feb 26, 2024): > Thanks for the report! This was an intentional decision, based on how other terminal emulators work. I went and dug up some of our older discussions to give you more context. 😄 > > Here's the short version: > > * xterm 331 chose to brighten 256-indexed colors 0-7 > * xterm 348 silently reverted this behavior > * An issue was filed on libvte (engine powering gnome-terminal) documenting the above: [gitlab.gnome.org/GNOME/vte/-/issues/149](https://gitlab.gnome.org/GNOME/vte/-/issues/149) > * We have an issue discussing this: [Should the bold/bright attribute apply to SGR 38/48 indexed colors? #5384](https://github.com/microsoft/terminal/issues/5384) > > I'll tentatively close this one out as a /duplicate of #5384 😄 Stealing some notes from https://github.com/microsoft/terminal/issues/11507#issuecomment-943481690
claunia commented 2026-01-31 07:40:15 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Feb 26, 2024):

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 (Feb 26, 2024): 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! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
claunia commented 2026-01-31 07:40:17 +00:00
Author
Owner
Copy Link

@magus424 commented on GitHub (Feb 26, 2024):

@DHowett fair enough - I missed those older issues in my searching - appreciate the links :)

@magus424 commented on GitHub (Feb 26, 2024): @DHowett fair enough - I missed those older issues in my searching - appreciate the links :)
claunia commented 2026-01-31 07:40:19 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 26, 2024):

No problem! It's good for us to get refreshed on these things too. I feel like we should have documentation for which "stances" we have taken on potentially-controversial issues in terminal emulation.

@DHowett commented on GitHub (Feb 26, 2024): No problem! It's good for us to get refreshed on these things too. I feel like we should have documentation for which "stances" we have taken on potentially-controversial issues in terminal emulation.
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#21315
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?