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

🐛 Solarized Dark theme renders certain commands/text unreadable. #8124

New Issue
Closed
opened 2026-01-31 01:21:17 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 01:21:17 +00:00
Owner
Copy Link

Originally created by @MiniFlames on GitHub (May 13, 2020).

Certain text is unreadable when using the 'Solarized Dark' theme, for example the following command in Powershell

pktmon start --etw -m real-time

is rendered like this:

image

Thus far I've only noticed the issue with Powershell commands.

Windows
Terminal Version(s): 0.11.1121.0 and 0.11.1333.0
Powershell Version: Powershell Core 7.0.0
Windows Version: Windows 10 - Insider Preview (Fast Ring), build 19268.

Originally created by @MiniFlames on GitHub (May 13, 2020). Certain text is unreadable when using the 'Solarized Dark' theme, for example the following command in Powershell `pktmon start --etw -m real-time` is rendered like this: ![image](https://user-images.githubusercontent.com/7881404/81873482-c6f5da00-9573-11ea-84e1-8ba06acad190.png) Thus far I've only noticed the issue with Powershell commands. --- Windows Terminal Version(s): 0.11.1121.0 and 0.11.1333.0 Powershell Version: Powershell Core 7.0.0 Windows Version: Windows 10 - Insider Preview (Fast Ring), build 19268.
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 01:21:17 +00:00
claunia commented 2026-01-31 01:21:18 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (May 14, 2020):

I've experienced this once with PSCore. Changing the color setting of PSCore itself (using Set-PSReadlineOption) effectively fix this. I'm not sure what we can do (or should do) on the terminal side.

@skyline75489 commented on GitHub (May 14, 2020): I've experienced this once with PSCore. Changing the color setting of PSCore itself (using `Set-PSReadlineOption`) effectively fix this. I'm not sure what we can do (or should do) on the terminal side.
claunia commented 2026-01-31 01:21:18 +00:00
Author
Owner
Copy Link

@jdhitsolutions commented on GitHub (May 14, 2020):

I have found that when using this theme I have to make sure not to set useAcrylic to false and remove the PSReadline module. The problem is the conflict between PSReadline options and the WT theme. I'm not sure that can be fixed. I'd say your best solution is to use Set-PSReadlineOption to adjust colors when using the Solarized Dark theme.

@jdhitsolutions commented on GitHub (May 14, 2020): I have found that when using this theme I have to make sure not to set useAcrylic to false and remove the PSReadline module. The problem is the conflict between PSReadline options and the WT theme. I'm not sure that can be fixed. I'd say your best solution is to use `Set-PSReadlineOption` to adjust colors when using the Solarized Dark theme.
claunia commented 2026-01-31 01:21:18 +00:00
Author
Owner
Copy Link

@jdhitsolutions commented on GitHub (May 14, 2020):

This is the PowerShell script I run when I need to adjust colors.

#Update-PSReadline.ps1
# https://en.wikipedia.org/wiki/ANSI_escape_code

if ($IsCoreCLR) {
    $esc = "`e"
}
else {
    $esc = $([char]0x1b)
}

Set-PSReadLineOption -Colors @{
    Parameter = "$esc[96m"
    Operator  = "$esc[38;5;47m"
    comment   = "$esc[92m"
    String    = "$esc[38;5;51m"
}
@jdhitsolutions commented on GitHub (May 14, 2020): This is the PowerShell script I run when I need to adjust colors. ```powershell #Update-PSReadline.ps1 # https://en.wikipedia.org/wiki/ANSI_escape_code if ($IsCoreCLR) { $esc = "`e" } else { $esc = $([char]0x1b) } Set-PSReadLineOption -Colors @{ Parameter = "$esc[96m" Operator = "$esc[38;5;47m" comment = "$esc[92m" String = "$esc[38;5;51m" } ```
claunia commented 2026-01-31 01:21:19 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (May 14, 2020):

This is a very old bug in the Solarized color scheme (https://github.com/altercation/solarized/issues/220).

@j4james commented on GitHub (May 14, 2020): This is a very old bug in the Solarized color scheme (https://github.com/altercation/solarized/issues/220).
claunia commented 2026-01-31 01:21:19 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 15, 2020):

Yeah, this one is unfortunately by design. Solarized was not a good color scheme for us to ship by default, but here we are on the doorstep of v1 being sad about it. ☹️

@DHowett-MSFT commented on GitHub (May 15, 2020): Yeah, this one is unfortunately by design. Solarized was _not_ a good color scheme for us to ship by default, but here we are on the doorstep of v1 being sad about it. ☹️
claunia commented 2026-01-31 01:21:19 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 15, 2020):

FWIW: some combination of #2661 and #293 are at play here.

@DHowett-MSFT commented on GitHub (May 15, 2020): FWIW: some combination of #2661 and #293 are at play here.
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-Question Needs-Tag-Fix Resolution-Answered
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#8124
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?