starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 07:54:35 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

I can't change red color. Is this bug? #18282

New Issue
Closed
opened 2026-01-31 06:09:15 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 06:09:15 +00:00
Owner
Copy Link

Originally created by @CatCatCatDog on GitHub (Aug 23, 2022).

Windows Terminal version

1.14.1962.0

Windows build number

19044.1889

Other Software

demsg
I can't change red color in Windows Terminal.
As you can see, segmention fault error message is red color in Windows Terminal.
This red color is too dark. So, I chaged json file "red":"#FF0000" to "red":"#FFFFFF".

white
I can't change more light colors like this.

Steps to reproduce

I chaged json file "red":"#FF0000" to "red":"#FFFFFF" or "red":"#FFF000" or "red":"#FF1000" or "red":"#FF5000".

Expected Behavior

No response

Actual Behavior

Must change more light red.

Originally created by @CatCatCatDog on GitHub (Aug 23, 2022). ### Windows Terminal version 1.14.1962.0 ### Windows build number 19044.1889 ### Other Software ![demsg](https://user-images.githubusercontent.com/23658192/186140511-ce1c398a-ab28-45f2-84e3-bc0feb65406f.png) I can't change red color in Windows Terminal. As you can see, segmention fault error message is red color in Windows Terminal. This red color is too dark. So, I chaged json file "red":"#FF0000" to "red":"#FFFFFF". ![white](https://user-images.githubusercontent.com/23658192/186141079-f14a13a6-b0c5-4269-a88b-bf87abfe0887.png) I can't change more light colors like this. ### Steps to reproduce I chaged json file "red":"#FF0000" to "red":"#FFFFFF" or "red":"#FFF000" or "red":"#FF1000" or "red":"#FF5000". ### Expected Behavior _No response_ ### Actual Behavior Must change more light red.
claunia commented 2026-01-31 06:09:17 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 23, 2022):

I suspect they're printing text with the "faint" attribute set (see #6703). Which shell are you using/? I can whip up a quick test script to compare.

@zadjii-msft commented on GitHub (Aug 23, 2022): I suspect they're printing text with the "faint" attribute set (see #6703). Which shell are you using/? I can whip up a quick test script to compare.
claunia commented 2026-01-31 06:09:17 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 23, 2022):

A very simple test:

printf "\x1b[31m_NORMAL_\x1b[m\n\x1b[2;31m_FAINT_\x1bm\n"

image

(on a better background)
image

So the application itself is likely just emitting text and specifically telling the Terminal "make this text fainter".

EDIT: I see my typo now, it should be \x1b[m\n at the end but I'm gonna leave it instead of just taking new screenshots

@zadjii-msft commented on GitHub (Aug 23, 2022): A very simple test: ```bash printf "\x1b[31m_NORMAL_\x1b[m\n\x1b[2;31m_FAINT_\x1bm\n" ``` ![image](https://user-images.githubusercontent.com/18356694/186142577-cf9d816e-fb39-4fa8-8467-0feeb8311e82.png) (on a better background) ![image](https://user-images.githubusercontent.com/18356694/186142732-f7f7d85e-d94d-454e-b740-86494048d0d8.png) So the application itself is likely just emitting text and specifically telling the Terminal "make this text fainter". EDIT: I see my typo now, it should be `\x1b[m\n` at the end but I'm gonna leave it instead of just taking new screenshots
claunia commented 2026-01-31 06:09:17 +00:00
Author
Owner
Copy Link

@CatCatCatDog commented on GitHub (Aug 23, 2022):

Yeah, I think so, This is faint text problem.
I use bash in Linux.
How to fix this problem?
제목 없음

@CatCatCatDog commented on GitHub (Aug 23, 2022): Yeah, I think so, This is faint text problem. I use bash in Linux. How to fix this problem? ![제목 없음](https://user-images.githubusercontent.com/23658192/186149597-257cc866-b2cc-421b-8e65-8f901e4bd8e9.png)
claunia commented 2026-01-31 06:09:17 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 23, 2022):

There is no problem - we're obeying what the application told us to render to the screen. They wanted faint, we gave them faint. If you don't want that application to emit faint text to the terminal, you should probably file an issue/request with them 😉

@zadjii-msft commented on GitHub (Aug 23, 2022): There is no problem - we're obeying what the application told us to render to the screen. They wanted faint, we gave them faint. If you don't want that application to emit faint text to the terminal, you should probably file an issue/request with them 😉
claunia commented 2026-01-31 06:09:17 +00:00
Author
Owner
Copy Link

@CatCatCatDog commented on GitHub (Aug 23, 2022):

Okay :)

@CatCatCatDog commented on GitHub (Aug 23, 2022): Okay :)
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-Attention Needs-Tag-Fix 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#18282
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?