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

Numbers are invisible with some themes in PowerShell #16252

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

Originally created by @IvanRenison on GitHub (Dec 23, 2021).

If I type in PowerShell with windows terminal:

PS C:\> 2+3

With the theme One Half Light or Solarized Light the numbers seem to be the same colour as the background.
Here some examples:

With One Half Light:
image

With Solarized Light:
image

Also, with Tango Light is almost invisible:
image

And here is with Campbell Powershell for reference:
image

I suppose that what is happening is that these theme's have de colour that PowerShell uses for numbers as the same colour than the background.

I have windows terminal version 1.11.2921.0, windows build number 10.0.19042.0, and I have not changed the colors of the themes.

Originally created by @IvanRenison on GitHub (Dec 23, 2021). If I type in PowerShell with windows terminal: ``` PS C:\> 2+3 ``` With the theme `One Half Light` or `Solarized Light` the numbers seem to be the same colour as the background. Here some examples: With `One Half Light`: ![image](https://user-images.githubusercontent.com/85908989/147286323-003deed8-f428-490d-9f59-18d0afd950ca.png) With `Solarized Light`: ![image](https://user-images.githubusercontent.com/85908989/147286346-a7f1418e-9aad-4a43-bb39-e3c90701b870.png) Also, with `Tango Light` is almost invisible: ![image](https://user-images.githubusercontent.com/85908989/147286488-3feda044-2538-4ac7-8932-043d7df6f4c3.png) And here is with `Campbell Powershell` for reference: ![image](https://user-images.githubusercontent.com/85908989/147286553-511ab21a-fe3c-4a55-84dc-9dc3363c0077.png) I suppose that what is happening is that these theme's have de colour that PowerShell uses for numbers as the same colour than the background. I have windows terminal version `1.11.2921.0`, windows build number `10.0.19042.0`, and I have not changed the colors of the themes.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 05:01:47 +00:00
claunia commented 2026-01-31 05:01:48 +00:00
Author
Owner
Copy Link

@237dmitry commented on GitHub (Dec 23, 2021):

I think this is PSReadline settings. Try:

Set-PSReadLineOption -Colors @{ 'Number' = "`e[1;30m" }             # PowerShell Core
Set-PSReadLineOption -Colors @{ 'Number' = "$([char]27)[1;30m"  }   # Windows PowerShell
@237dmitry commented on GitHub (Dec 23, 2021): I think this is PSReadline settings. Try: ``` Set-PSReadLineOption -Colors @{ 'Number' = "`e[1;30m" } # PowerShell Core Set-PSReadLineOption -Colors @{ 'Number' = "$([char]27)[1;30m" } # Windows PowerShell ```
claunia commented 2026-01-31 05:01:48 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Dec 23, 2021):

If you're willing to use the Windows Terminal preview build, there is an option on the profile appearance tab, "Automatically adjust lightness of indistinguishable text", which does a reasonable job of fixing broken color schemes like this.

@j4james commented on GitHub (Dec 23, 2021): If you're willing to use the Windows Terminal preview build, there is an option on the profile appearance tab, "Automatically adjust lightness of indistinguishable text", which does a reasonable job of fixing broken color schemes like this.
claunia commented 2026-01-31 05:01:49 +00:00
Author
Owner
Copy Link

@IvanRenison commented on GitHub (Dec 23, 2021):

I think this is PSReadline settings. Try:

Set-PSReadLineOption -Colors @{ 'Number' = "`e[1;30m" }             # PowerShell Core
Set-PSReadLineOption -Colors @{ 'Number' = "$([char]27)[1;30m"  }   # Windows PowerShell

That worked, thank you

Good to know than for future versions there will be a better solution

@IvanRenison commented on GitHub (Dec 23, 2021): > I think this is PSReadline settings. Try: > > ``` > Set-PSReadLineOption -Colors @{ 'Number' = "`e[1;30m" } # PowerShell Core > Set-PSReadLineOption -Colors @{ 'Number' = "$([char]27)[1;30m" } # Windows PowerShell > ``` That worked, thank you Good to know than for future versions there will be a better solution
claunia commented 2026-01-31 05:01:49 +00:00
Author
Owner
Copy Link

@cloudbaseaws commented on GitHub (Jul 2, 2024):

Worked!

@cloudbaseaws commented on GitHub (Jul 2, 2024): Worked!
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#16252
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?