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

Incorrect color for white #10074

New Issue
Closed
opened 2026-01-31 02:11:48 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 02:11:48 +00:00
Owner
Copy Link

Originally created by @wawaforya on GitHub (Aug 8, 2020).

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.18363.0 Microsoft Windows NT 10.0.18363.0

Windows Terminal version (if applicable):
(Installed via Scoop, https://scoop.sh/)
Windows Terminal (Unpackaged)
Version: 1.1.200720001-release1.1

Any other software?
No.

Steps to reproduce

  1. Configure a color scheme as shown in the picture. Also refer to this gist for the details.
    Colorscheme

  2. Open a new PowerShell or PowerShell Core tab in Windows Terminal and run a script.

$esc = "$([char]27)"; for ($i = 30; $i -le 37; $i++) { Write-Host "$esc[${i}mNormal: (0;$i); $esc[${i};1mBright: (1;$i)" }

The color for Normal: (0;37); should be #a0a0a0 as configured, while it's displayed in black.
PowerShell
PowerShell Core

Or open a WSL tab (I use Arch Linux personally) and run a script.

for ((i = 30; i < 38; i++ )); do echo -e "\033[0;"$i"m Normal: (0;$i); \033[1;"$i"m Light: (1;$i)"; done

The color for Normal: (0;37); has the same issue as PowerShell.
WSL Arch

Expected behavior

The color for Normal: (0;37); should be displayed in #a0a0a0 as configured.

Actual behavior

The color for Normal: (0;37); is incorrect.

Originally created by @wawaforya on GitHub (Aug 8, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 Windows Terminal version (if applicable): (Installed via Scoop, https://scoop.sh/) Windows Terminal (Unpackaged) Version: 1.1.200720001-release1.1 Any other software? No. ``` # Steps to reproduce 1. Configure a color scheme as shown in the picture. Also refer to [this gist](https://gist.github.com/wawaforya/0c2de893d91730421c0e572843b7e9cf) for the details. ![Colorscheme](https://user-images.githubusercontent.com/19285014/89710760-4c90f680-d9b8-11ea-8aea-34a9024ef9ac.png) 2. Open a new PowerShell or PowerShell Core tab in Windows Terminal and run a script. ```powershell $esc = "$([char]27)"; for ($i = 30; $i -le 37; $i++) { Write-Host "$esc[${i}mNormal: (0;$i); $esc[${i};1mBright: (1;$i)" } ``` The color for `Normal: (0;37);` should be #a0a0a0 as configured, while it's displayed in black. ![PowerShell](https://user-images.githubusercontent.com/19285014/89711016-37b56280-d9ba-11ea-8930-d0ae71c5688f.png) ![PowerShell Core](https://user-images.githubusercontent.com/19285014/89711021-3b48e980-d9ba-11ea-82d8-63345b80d58d.png) Or open a WSL tab (I use Arch Linux personally) and run a script. ```bash for ((i = 30; i < 38; i++ )); do echo -e "\033[0;"$i"m Normal: (0;$i); \033[1;"$i"m Light: (1;$i)"; done ``` The color for `Normal: (0;37);` has the same issue as PowerShell. ![WSL Arch](https://user-images.githubusercontent.com/19285014/89711024-3d12ad00-d9ba-11ea-8d65-8e1b65e2bdf7.png) <!-- A description of how to trigger this bug. --> # Expected behavior The color for `Normal: (0;37);` should be displayed in #a0a0a0 as configured. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior The color for `Normal: (0;37);` is incorrect. <!-- What's actually happening? -->
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 02:11:48 +00:00
claunia commented 2026-01-31 02:11:49 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Aug 8, 2020):

Considering the version number you're on, this is probably a symptom of issue #2661, which was fixed in v1.2.2022.0. That said, upgrading isn't really going to help, because we still have a color compatibility hack in place for PowerShell (PR #6810) that retains that incorrect color, because fixing it makes things worse. If you're using the cmd shell or a WSL shell, though, the colors should be correct in the latest preview version of WT.

@j4james commented on GitHub (Aug 8, 2020): Considering the version number you're on, this is probably a symptom of issue #2661, which was fixed in v1.2.2022.0. That said, upgrading isn't really going to help, because we still have a color compatibility hack in place for PowerShell (PR #6810) that retains that incorrect color, because fixing it makes things worse. If you're using the cmd shell or a WSL shell, though, the colors should be correct in the latest preview version of WT.
claunia commented 2026-01-31 02:11:50 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Aug 8, 2020):

For reference, here's what your WSL test case looks like in the latest version:
image

@j4james commented on GitHub (Aug 8, 2020): For reference, here's what your WSL test case looks like in the latest version: ![image](https://user-images.githubusercontent.com/4181424/89715150-ccf52e80-d99b-11ea-973d-ce52fa6698dd.png)
claunia commented 2026-01-31 02:11:50 +00:00
Author
Owner
Copy Link

@wawaforya commented on GitHub (Aug 8, 2020):

@j4james, thanks you very much. Just installed the latest preview version and it works fine in WSL now.

@wawaforya commented on GitHub (Aug 8, 2020): @j4james, thanks you very much. Just installed the latest preview version and it works fine in WSL now.
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 Needs-Tag-Fix 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#10074
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?