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

Number parameters in Powershell are barely visible under light color schemes. #13255

New Issue
Closed
opened 2026-01-31 03:37:52 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 03:37:52 +00:00
Owner
Copy Link

Originally created by @CyanideCentral on GitHub (Mar 31, 2021).

Environment

Windows version: 18363.1440
Terminal version: 1.6.10571.0

Steps to reproduce

Set color theme to light color schemes, such as One Half Light, Tango Light or 3rd party light themes.
Enter command "abcd 1234" in a Powershell tab, or simply "1234". Weirdly this doesn't happen in CMD tabs.

Expected behavior

I should be able to see the number displayed on screen.

Actual behavior

I can barely tell the number from the white background. Effects of entering "abcd 1234":

One Half Light

image
I actually entered '1234' after the 'abcd '.

Tango Light

image
Slightly better, but not clear at all.

Proposed solution

Change the color setting for numbers entered in Powershell.

Related to

#8033 #8716

Originally created by @CyanideCentral on GitHub (Mar 31, 2021). # Environment Windows version: 18363.1440 Terminal version: 1.6.10571.0 # Steps to reproduce Set color theme to light color schemes, such as One Half Light, Tango Light or 3rd party light themes. Enter command "abcd 1234" in a Powershell tab, or simply "1234". Weirdly this doesn't happen in CMD tabs. # Expected behavior I should be able to see the number displayed on screen. # Actual behavior I can barely tell the number from the white background. Effects of entering "abcd 1234": ### One Half Light ![image](https://user-images.githubusercontent.com/25578198/113111694-046e5f00-923b-11eb-836b-a3952cb04216.png) I actually entered '1234' after the 'abcd '. ### Tango Light ![image](https://user-images.githubusercontent.com/25578198/113111878-31227680-923b-11eb-8c8c-b5e1849c7309.png) Slightly better, but not clear at all. # Proposed solution Change the color setting for numbers entered in Powershell. # Related to #8033 #8716
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 03:37:52 +00:00
claunia commented 2026-01-31 03:37:53 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Mar 31, 2021):

As Dustin pointed out in https://github.com/microsoft/terminal/issues/8033#issuecomment-716058667 , this is actually by design. You'll need to do some configuring to make the color-emitting application more suitable for your needs.

@skyline75489 commented on GitHub (Mar 31, 2021): As Dustin pointed out in https://github.com/microsoft/terminal/issues/8033#issuecomment-716058667 , this is actually by design. You'll need to do some configuring to make the color-emitting application more suitable for your needs.
claunia commented 2026-01-31 03:37:53 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 31, 2021):

Yea, this is by design. PSReadline's default config for text attributes doesn't really work all that well with light themes.

@zadjii-msft commented on GitHub (Mar 31, 2021): Yea, this is by design. PSReadline's default config for text attributes doesn't really work all that well with light themes.
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#13255
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?