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

Windows Terminal mess up colors in a command line when use "One Half Light" color scheme #23114

New Issue
Closed
opened 2026-01-31 08:32:50 +00:00 by claunia · 11 comments
claunia commented 2026-01-31 08:32:50 +00:00
Owner
Copy Link

Originally created by @schicout on GitHub (Apr 2, 2025).

Windows Terminal version

1.22.10731.0

Windows build number

10.0.19045.0

Other Software

No response

Steps to reproduce

1 Open windows terminal
2 Print something

Image

3 ... then clear it with BackSpace key.

Image

4 Type some commands with args

Image

5 There is no spaces:

Image

... there is (select text by ctrl+shift+left):

Image

I think that's enough, this is probably another view of the same bugs that were described here earlier. I apologize if I'm repeating already opened issues, but I couldn't find a description of this exact behavior right away.

Expected Behavior

No response

Actual Behavior

Described in Steps to reproduce

Originally created by @schicout on GitHub (Apr 2, 2025). ### Windows Terminal version 1.22.10731.0 ### Windows build number 10.0.19045.0 ### Other Software _No response_ ### Steps to reproduce 1 Open windows terminal 2 Print something ![Image](https://github.com/user-attachments/assets/56613289-ffaa-4f99-8606-50d26d88b5f4) 3 ... then clear it with BackSpace key. ![Image](https://github.com/user-attachments/assets/4e2ec52c-ffa9-49fa-8ef8-e52de02fca91) 4 Type some commands with args ![Image](https://github.com/user-attachments/assets/6a31a380-a043-4257-906f-2660808fef98) 5 There is no spaces: ![Image](https://github.com/user-attachments/assets/33499897-79c1-454a-b6c1-4884037eff1b) ... there is (select text by ctrl+shift+left): ![Image](https://github.com/user-attachments/assets/a8fb06e4-306c-4fc2-ad49-afd99803a92a) I think that's enough, this is probably another view of the same bugs that were described here earlier. I apologize if I'm repeating already opened issues, but I couldn't find a description of this exact behavior right away. ### Expected Behavior _No response_ ### Actual Behavior Described in _Steps to reproduce_
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 08:32:50 +00:00
claunia commented 2026-01-31 08:32:51 +00:00
Author
Owner
Copy Link

@Stranger-Jie commented on GitHub (Apr 3, 2025):

i also meet this issue. i have tried init and reinstall, but didn't work.

Image

@Stranger-Jie commented on GitHub (Apr 3, 2025): i also meet this issue. i have tried init and reinstall, but didn't work. ![Image](https://github.com/user-attachments/assets/3d8cc6a9-41e2-4b1f-af1c-d21fbd170905)
claunia commented 2026-01-31 08:32:51 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Apr 3, 2025):

See the troubleshooting page here: Black lines in PowerShell.

@j4james commented on GitHub (Apr 3, 2025): See the troubleshooting page here: [Black lines in PowerShell](https://learn.microsoft.com/en-us/windows/terminal/troubleshooting#black-lines-in-powershell-51-6x-70).
claunia commented 2026-01-31 08:32:51 +00:00
Author
Owner
Copy Link

@schicout commented on GitHub (Apr 3, 2025):

Version of PSReadline is 2.0.0 actually.

Image

Trying to update PSReadline follows to:

Image
(The module 'PSReadLine' isn't installed using the Install-Module command, so it cannot be updated.)

When trying to install a PSReadLine using the Install-Module command, a message is displayed that "Untrusted repository. Installing modules from an untrusted repository. If you trust this repository, change its InstallationPolicy value by running the Set-PSRepository cmdlet. Do you really want to install modules from "PSGallery"?" I have all the security settings "by default". Is it ok that the PSGallery is considered an "Untrusted" repo by default? Should I change security policy to this repo? Is it safe?

Image

@schicout commented on GitHub (Apr 3, 2025): Version of PSReadline is 2.0.0 actually. ![Image](https://github.com/user-attachments/assets/675fd784-948e-4a9a-bba6-9a0a0dcd4921) Trying to update PSReadline follows to: ![Image](https://github.com/user-attachments/assets/7e431377-8962-4098-9c10-9ac19aace0b8) (The module 'PSReadLine' isn't installed using the Install-Module command, so it cannot be updated.) When trying to install a PSReadLine using the Install-Module command, a message is displayed that "Untrusted repository. Installing modules from an untrusted repository. If you trust this repository, change its InstallationPolicy value by running the Set-PSRepository cmdlet. Do you really want to install modules from "PSGallery"?" I have all the security settings "by default". Is it ok that the PSGallery is considered an "Untrusted" repo by default? Should I change security policy to this repo? Is it safe? ![Image](https://github.com/user-attachments/assets/b6a9d1da-cfbe-47a5-8ad0-d8e3c0e43a15)
claunia commented 2026-01-31 08:32:51 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Apr 3, 2025):

@schicout I'm guessing you're using the PowerShell that came bundled with Windows 10. I believe the PSReadLine included with that is actually a beta version of 2.0.0, which is why it still has this bug. I'm not a PowerShell expert, so I don't know why the update doesn't work for you (possibly because it's a bundled version), but I found a comment in another thread from someone explaining how they got it to update. See https://github.com/microsoft/terminal/issues/18624#issuecomment-2680719168.

@j4james commented on GitHub (Apr 3, 2025): @schicout I'm guessing you're using the PowerShell that came bundled with Windows 10. I believe the PSReadLine included with that is actually a beta version of 2.0.0, which is why it still has this bug. I'm not a PowerShell expert, so I don't know why the update doesn't work for you (possibly because it's a bundled version), but I found a comment in another thread from someone explaining how they got it to update. See https://github.com/microsoft/terminal/issues/18624#issuecomment-2680719168.
claunia commented 2026-01-31 08:32:51 +00:00
Author
Owner
Copy Link

@schicout commented on GitHub (Apr 3, 2025):

Regarding the bug, two pieces of news.
Good. It seems I managed to localize the problem a little more. It turns out that the bug is reproduced only on color scheme "One Half Light", on schemes "Solarized Light" and "Tango Light" everything works without errors. So it looks like this is some kind of bug in the themes.

Solarized Light:
Image
Tango Light
Image

Not so good. Updating the module PSReadline (@j4james - thanks for the tip!) only resulted in the text being written white-on-white instead of black-on-black. So imho the bug does exist.
One Half Light:
Image

@schicout commented on GitHub (Apr 3, 2025): Regarding the bug, two pieces of news. **Good**. It seems I managed to localize the problem a little more. It turns out that the bug is reproduced only on color scheme "One Half Light", on schemes "Solarized Light" and "Tango Light" everything works without errors. So it looks like this is some kind of bug in the themes. Solarized Light: ![Image](https://github.com/user-attachments/assets/dafce443-1016-4f94-9688-a076ccbbc822) Tango Light ![Image](https://github.com/user-attachments/assets/9c27ecd5-cf05-4715-ad38-7172b3e47baf) **Not so good**. Updating the module PSReadline (@j4james - thanks for the tip!) only resulted in the text being written white-on-white instead of black-on-black. So imho the bug does exist. One Half Light: ![Image](https://github.com/user-attachments/assets/3d021bf7-aa53-4416-afd0-76243814291b)
claunia commented 2026-01-31 08:32:52 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Apr 3, 2025):

It turns out that the bug is reproduced only on color scheme "One Half Light"

This is just a limitation of that color scheme. Their default background color is identical to their white color, which makes that color combination invisible - there's nothing the terminal can do about that. You can always tweak the color scheme yourself, choose a scheme that works better with PowerShell, or possibly tweak the PowerShell color mappings (I'm not sure if this is for the right version, but there's a guide here).

@j4james commented on GitHub (Apr 3, 2025): > It turns out that the bug is reproduced only on color scheme "One Half Light" This is just a limitation of that color scheme. Their default background color is identical to their white color, which makes that color combination invisible - there's nothing the terminal can do about that. You can always tweak the color scheme yourself, choose a scheme that works better with PowerShell, or possibly tweak the PowerShell color mappings (I'm not sure if this is for the right version, but there's a guide [here](https://learn.microsoft.com/en-us/powershell/scripting/learn/shell/using-light-theme?view=powershell-5.1)).
claunia commented 2026-01-31 08:32:52 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 9, 2025):

This is just a limitation of that color scheme.

Alas, this is true. This bug is by design.

You may want to enable the "Adjust indistinguishable colors" feature, as you will run into a lot of application that don't render properly with light themes.

/dup #15452

@DHowett commented on GitHub (Apr 9, 2025): > This is just a limitation of that color scheme. Alas, this is true. This bug is by design. You may want to enable the "Adjust indistinguishable colors" feature, as you will run into a lot of application that don't render properly with light themes. /dup #15452
claunia commented 2026-01-31 08:32:52 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Apr 9, 2025):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Apr 9, 2025): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
claunia commented 2026-01-31 08:32:52 +00:00
Author
Owner
Copy Link

@mangelozzi commented on GitHub (Nov 10, 2025):

I tried changing from Half light to Solarized and I still barely can see:

Image as shown below:

@mangelozzi commented on GitHub (Nov 10, 2025): I tried changing from Half light to Solarized and I still barely can see: <img width="864" height="416" alt="Image" src="https://github.com/user-attachments/assets/fe7c7fdb-7fc8-4df5-85e3-1b33e4da2014" /> as shown below:
claunia commented 2026-01-31 08:32:52 +00:00
Author
Owner
Copy Link

@schicout commented on GitHub (Nov 10, 2025):

As DHowett says - "This bug is by design."
I "resolved" (if it can be called that) issue by assigning the same values to the 'Black' and 'Background' colors (I'm using a dark color scheme based on GitHub's dark theme, whether you can hack the light scheme in the same way — I don't know).
But IMHO, this is just a hack. What I really need is a proper application-level fix, not just a color scheme change. But eh, it'll do.

@schicout commented on GitHub (Nov 10, 2025): As DHowett says - "This bug is by design." I "resolved" (if it can be called that) issue by assigning the same values to the 'Black' and 'Background' colors (I'm using a dark color scheme based on GitHub's dark theme, whether you can hack the light scheme in the same way — I don't know). But IMHO, this is just a hack. What I really need is a proper application-level fix, not just a color scheme change. But eh, it'll do.
claunia commented 2026-01-31 08:32:52 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 10, 2025):

DAYS SINCE I'VE REGRETTED SHIPPING SOLARIZED: 258 0

@zadjii-msft commented on GitHub (Nov 10, 2025): ### [DAYS SINCE I'VE REGRETTED SHIPPING SOLARIZED: ~~258~~ 0](https://github.com/microsoft/terminal/issues/18617#issuecomment-2683460213)
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 Resolution-Duplicate
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#23114
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?