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

brightBlack and black color values from Solarized Dark Color Scheme are swapped #19209

New Issue
Open
opened 2026-01-31 06:36:57 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 06:36:57 +00:00
Owner
Copy Link

Originally created by @nachopitt on GitHub (Jan 15, 2023).

Windows Terminal version

1.15.3465.0

Windows build number

No response

Other Software

VSCode 1.74.2 with Solarized Dark Color Theme selected
vim 8.1.2262 (inside WSL2)
colortest-256

Steps to reproduce

According to the colors table in https://en.wikipedia.org/wiki/Solarized

image

the Solarized Dark Color Scheme default values should be
black = #073642
brBlack = #002b36

In VSCode Terminal running in WSL2: Ubuntu-20.04 the color schema seems to be correct. But running the same WSL2 Distro but this time in Windows Terminal, the black and brBlack colors are swapped.

You can visually confirm this by running the colortest-256 test application on both environments:

VSCode Terminal:
image

Windows Terminal:
image

Expected Behavior

Both VSCode and Windows Terminal should be able to reproduce the same colors when selecting the same Color Theme/Schema (In this case, Solarized Dark).

I know this can be easily solved at "user configuration" level, but it would be better to have the correct values by default.

Actual Behavior

By using vim, the color swap effect is more noticeable

VSCode Terminal
image

Windows Terminal
image

Originally created by @nachopitt on GitHub (Jan 15, 2023). ### Windows Terminal version 1.15.3465.0 ### Windows build number _No response_ ### Other Software VSCode 1.74.2 with Solarized Dark Color Theme selected vim 8.1.2262 (inside WSL2) colortest-256 ### Steps to reproduce According to the colors table in https://en.wikipedia.org/wiki/Solarized ![image](https://user-images.githubusercontent.com/12923928/212559095-e05ff8f7-6954-4abe-abd9-c05ad49b1938.png) the Solarized Dark Color Scheme default values should be **black = #073642** **brBlack = #002b36** In VSCode Terminal running in WSL2: Ubuntu-20.04 the color schema seems to be correct. But running the same WSL2 Distro but this time in Windows Terminal, the black and brBlack colors are swapped. You can visually confirm this by running the colortest-256 test application on both environments: VSCode Terminal: ![image](https://user-images.githubusercontent.com/12923928/212560083-55c18a21-5bf5-4248-9802-f2bc8100acdd.png) Windows Terminal: ![image](https://user-images.githubusercontent.com/12923928/212560124-d419e777-845f-4ba5-900a-3e9673750af0.png) ### Expected Behavior Both VSCode and Windows Terminal should be able to reproduce the same colors when selecting the same Color Theme/Schema (In this case, Solarized Dark). I know this can be easily solved at "user configuration" level, but it would be better to have the correct values by default. ### Actual Behavior By using vim, the color swap effect is more noticeable VSCode Terminal ![image](https://user-images.githubusercontent.com/12923928/212560200-8f61f090-1413-459e-bb84-1202d926daf1.png) Windows Terminal ![image](https://user-images.githubusercontent.com/12923928/212560170-e84ccee5-d7e5-4132-92b2-404610fa9fca.png)
claunia added the Resolution-By-DesignNeeds-TriageIssue-Bug labels 2026-01-31 06:36: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 Issue-Bug Needs-Triage Resolution-By-Design
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#19209
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?