starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Git branch name text color cannot be controlled from properties menu #6908

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

Originally created by @ianHunterClipd on GitHub (Mar 16, 2020).

Environment

Windows build number:
Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0

Windows Terminal version (if applicable):
Ubuntu

Any other software?
git

Steps to reproduce

Create a new git repo and initialize or step into an existing git repo.
Use git branch to display current working branch

Expected behavior

The branch names for the given repo should be listed, with the current working branch denoted by an asterisk. It would seem that the color of the branch name text should be controlled by the same terminal properties that control the other text colors in the terminal, namely
Colors --> Screen Text and Colors --> Popup text

Actual behavior

The branch names are displayed in a single color that is independent of the font color for the terminal.
gitBranchColor
In the image above, both of my text color settings in the Properties --> Colors window have been set to red, which is reflected in the user input in the terminal. However, the color of the branch name remains black. For light colored backgrounds this is not a problem - I noticed the issue when trying to set the background to Ubuntu's default purple color.

Am I missing something simple? I have been using a custom color palette for the past two years, but earlier this week one of the Windows updates reset my Ubuntu terminal color preferences. After reverting to the colors in this article Ubuntu colors for windows bash the issue was immediately noticeable. Any advice would be greatly appreciated - I'll roll with a lighter color scheme for now but would much prefer my old palette back.

Cheers,
Ian

Originally created by @ianHunterClipd on GitHub (Mar 16, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment Windows build number: Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 Windows Terminal version (if applicable): Ubuntu Any other software? git # Steps to reproduce <!-- A description of how to trigger this bug. --> Create a new git repo and initialize or step into an existing git repo. Use `git branch` to display current working branch # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> The branch names for the given repo should be listed, with the current working branch denoted by an asterisk. It would seem that the color of the branch name text should be controlled by the same terminal properties that control the other text colors in the terminal, namely Colors --> Screen Text and Colors --> Popup text # Actual behavior <!-- What's actually happening? --> The branch names are displayed in a single color that is independent of the font color for the terminal. ![gitBranchColor](https://user-images.githubusercontent.com/42324272/76798245-74bf5500-678c-11ea-830c-5d0e5c27a266.png) In the image above, both of my text color settings in the Properties --> Colors window have been set to red, which is reflected in the user input in the terminal. However, the color of the branch name remains black. For light colored backgrounds this is not a problem - I noticed the issue when trying to set the background to Ubuntu's default purple color. Am I missing something simple? I have been using a custom color palette for the past two years, but earlier this week one of the Windows updates reset my Ubuntu terminal color preferences. After reverting to the colors in this article [Ubuntu colors for windows bash](https://medium.com/better-programming/make-bash-on-ubuntu-on-windows-10-look-like-the-ubuntu-terminal-f7566008c5c2) the issue was immediately noticeable. Any advice would be greatly appreciated - I'll roll with a lighter color scheme for now but would much prefer my old palette back. Cheers, Ian
claunia added the Product-ConhostIssue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 00:50:11 +00:00
claunia commented 2026-01-31 00:50:13 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 16, 2020):

Could you share what the contents of the "Terminal" tab in the console properties shows as well?

@zadjii-msft commented on GitHub (Mar 16, 2020): Could you share what the contents of the "Terminal" tab in the console properties shows as well?
claunia commented 2026-01-31 00:50:14 +00:00
Author
Owner
Copy Link

@ianHunterClipd commented on GitHub (Mar 16, 2020):

terminalPropertiesUbuntu

@ianHunterClipd commented on GitHub (Mar 16, 2020): ![terminalPropertiesUbuntu](https://user-images.githubusercontent.com/42324272/76799533-f2846000-678e-11ea-88d9-be26996cd655.png)
claunia commented 2026-01-31 00:50:15 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 16, 2020):

git likes to print the current branch name in color index 2 (which is usually green.)

normally:

image

your color scheme:

image

it appears as though you've swapped black and green.

@DHowett-MSFT commented on GitHub (Mar 16, 2020): git likes to print the current branch name in _color index 2_ (which is usually green.) normally: ![image](https://user-images.githubusercontent.com/14316954/76807247-f91bd300-67a0-11ea-86b0-017c6e29c2ea.png) your color scheme: ![image](https://user-images.githubusercontent.com/14316954/76807266-0d5fd000-67a1-11ea-9987-a2159de5a6af.png) it appears as though you've swapped black and green.
claunia commented 2026-01-31 00:50:15 +00:00
Author
Owner
Copy Link

@ianHunterClipd commented on GitHub (Mar 17, 2020):

Thank you so much!

Is there a reference available that maps each color index to its uses in the terminal? Curious for future changes.

@ianHunterClipd commented on GitHub (Mar 17, 2020): Thank you so much! Is there a reference available that maps each color index to its uses in the terminal? Curious for future changes.
claunia commented 2026-01-31 00:50:16 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 17, 2020):

Sure! The canonical meanings of all the color indices are here on Wikipedia for both the classic 16- and xterm 88/256-color palette.

@DHowett-MSFT commented on GitHub (Mar 17, 2020): Sure! The canonical meanings of all the color indices are [here on Wikipedia](https://en.wikipedia.org/wiki/ANSI_escape_code#Colors) for both the classic 16- and xterm 88/256-color palette.
claunia commented 2026-01-31 00:50:16 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 17, 2020):

Oh, if you're asking for a list of what colors applications typically use for what, I'm afraid that that would be a nigh-unto infinite list and one that might be very difficult to keep up to date 😄

@DHowett-MSFT commented on GitHub (Mar 17, 2020): Oh, if you're asking for a list of what colors applications typically use for what, I'm afraid that that would be a nigh-unto infinite list and one that might be very difficult to keep up to date :smile:
claunia commented 2026-01-31 00:50:16 +00:00
Author
Owner
Copy Link

@ianHunterClipd commented on GitHub (Mar 17, 2020):

Definitely was asking for something like the latter, but now that it's here the former is certainly a more informative read! Thanks again for your help 👍

@ianHunterClipd commented on GitHub (Mar 17, 2020): Definitely was asking for something like the latter, but now that it's here the former is certainly a more informative read! Thanks again for your help :+1:
claunia commented 2026-01-31 00:50:16 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 17, 2020):

I'm gonna go ahead and also pitch colortool here too, since editing all 16 colors by hand is a MAJOR pain, the kind of pain that colortool was specifically created to fix ☺️

@zadjii-msft commented on GitHub (Mar 17, 2020): I'm gonna go ahead and also pitch [colortool](https://github.com/microsoft/terminal/tree/master/src/tools/ColorTool) here too, since editing all 16 colors by hand is a MAJOR pain, the kind of pain that colortool was specifically created to fix ☺️
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 Product-Conhost 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#6908
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?