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

Colors & glyphs broken with git-for-windows bash #7090

New Issue
Closed
opened 2026-01-31 00:54:42 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 00:54:42 +00:00
Owner
Copy Link

Originally created by @niderhoff on GitHub (Mar 22, 2020).

Environment

Windows build number: 10.0.18363.0
Windows Terminal version (if applicable): 0.10.761.0

Any other software?
- Git for Windows v2.25.0 (January 13th 2020)

Steps to reproduce

  • Open vim in a git-bash shell

Expected behavior

Colors & glyphs work same as in WSL bash

Actual behavior

Background color is messed up, other colors are missing and different font-glyphs are replaced by squares:

image

As you can see it is only vim, the prompt is fine.

As a comparison, the same vim config in a WSL-bash environment:

image

Any ideas? Seems like some issue with mingw?
Here is the related profile:

            {
                "guid": "{269bed3e-4c58-495f-a318-3cfbadc27934}",
                "name" : "Git Bash",
                "commandline" : "C:\\Program Files\\Git\\bin\\bash.exe",
                "icon" : "C:\\Program Files\\Git\\mingw64\\share\\git\\git-for-windows.ico",
                "startingDirectory" : "C:\\Develop\\projects"
            },
Originally created by @niderhoff on GitHub (Mar 22, 2020). # Environment ```none Windows build number: 10.0.18363.0 Windows Terminal version (if applicable): 0.10.761.0 Any other software? - Git for Windows v2.25.0 (January 13th 2020) ``` # Steps to reproduce - Open vim in a git-bash shell # Expected behavior Colors & glyphs work same as in WSL bash # Actual behavior Background color is messed up, other colors are missing and different font-glyphs are replaced by squares: ![image](https://user-images.githubusercontent.com/5991543/77248617-1afed500-6c3b-11ea-933b-543c11e9633e.png) As you can see it is only vim, the prompt is fine. As a comparison, the same vim config in a WSL-bash environment: ![image](https://user-images.githubusercontent.com/5991543/77248643-53061800-6c3b-11ea-83fa-ca2591cf0dbc.png) Any ideas? Seems like some issue with mingw? Here is the related profile: ```json { "guid": "{269bed3e-4c58-495f-a318-3cfbadc27934}", "name" : "Git Bash", "commandline" : "C:\\Program Files\\Git\\bin\\bash.exe", "icon" : "C:\\Program Files\\Git\\mingw64\\share\\git\\git-for-windows.ico", "startingDirectory" : "C:\\Develop\\projects" }, ```
claunia added the Resolution-ExternalNeeds-Tag-Fix labels 2026-01-31 00:54:42 +00:00
claunia commented 2026-01-31 00:54:43 +00:00
Author
Owner
Copy Link

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

I believe this is a limitation of the MSYS2 runtime git-bash uses. Since the upstream MSYS2 runtime has been updated to support the Windows Console better, I expect that it will eventually be released as part of a Git for Windows update. Sorry!

@DHowett-MSFT commented on GitHub (Mar 24, 2020): I believe this is a limitation of the MSYS2 runtime git-bash uses. Since the upstream MSYS2 runtime has been updated to support the Windows Console better, I expect that it will eventually be released as part of a Git for Windows update. Sorry!
claunia commented 2026-01-31 00:54:44 +00:00
Author
Owner
Copy Link

@niderhoff commented on GitHub (Apr 7, 2020):

can you link me to the corresponding msys2 runtime update?

@niderhoff commented on GitHub (Apr 7, 2020): can you link me to the corresponding msys2 runtime update?
claunia commented 2026-01-31 00:54:44 +00:00
Author
Owner
Copy Link

@trajano commented on GitHub (May 19, 2020):

I tried using the latest msys2 from scoop using the following

        {
            "guid": "{00000000-0000-0000-ba54-000000000003}",
            "commandline" : "%UserProfile%/scoop/apps/msys2/current/usr/bin/bash.exe -i -l",
            "startingDirectory": "%UserProfile%",
            "name" : "MSys2"
        },

But running the test output still does not work correctly in Windows Terminal using

curl -s https://gist.githubusercontent.com/HaleTom/89ffe32783f89f403bba96bd7bcd1263/raw/ | bash
@trajano commented on GitHub (May 19, 2020): I tried using the latest msys2 from scoop using the following ``` { "guid": "{00000000-0000-0000-ba54-000000000003}", "commandline" : "%UserProfile%/scoop/apps/msys2/current/usr/bin/bash.exe -i -l", "startingDirectory": "%UserProfile%", "name" : "MSys2" }, ``` But running the test output still does not work correctly in Windows Terminal using ``` curl -s https://gist.githubusercontent.com/HaleTom/89ffe32783f89f403bba96bd7bcd1263/raw/ | bash ```
claunia commented 2026-01-31 00:54:44 +00:00
Author
Owner
Copy Link

@ean5533 commented on GitHub (Aug 26, 2020):

@DHowett-MSFT Based on the most recent comment above it sounds like there isn't actually an upstream fix. Do you have any further info?

@ean5533 commented on GitHub (Aug 26, 2020): @DHowett-MSFT Based on the most recent comment above it sounds like there isn't actually an upstream fix. Do you have any further info?
claunia commented 2026-01-31 00:54:44 +00:00
Author
Owner
Copy Link

@niderhoff commented on GitHub (Aug 26, 2020):

I am running the most recent .exe installer from git for windows and the most recent windows terminal (preview) from the microsoft store with MINGW64 (not msys) and colors now work fine.

So there might be still a problem with msys2?

@niderhoff commented on GitHub (Aug 26, 2020): I am running the most recent .exe installer from git for windows and the most recent windows terminal (preview) from the microsoft store with MINGW64 (not msys) and colors now work fine. So there might be still a problem with msys2?
claunia commented 2026-01-31 00:54:45 +00:00
Author
Owner
Copy Link

@trajano commented on GitHub (Aug 27, 2020):

Actually the current git bash works well it may have been fixed since the last time I tested it
image

Mind you it is very slow to run that bash script. I haven't determined whether it is bash or windows terminal issue. But bat also gets really slow.

@trajano commented on GitHub (Aug 27, 2020): Actually the current git bash works well it may have been fixed since the last time I tested it ![image](https://user-images.githubusercontent.com/110627/91378049-7b4b0180-e7ed-11ea-82e5-42736d039fbd.png) Mind you it is very slow to run that bash script. I haven't determined whether it is bash or windows terminal issue. But `bat` also gets really slow.
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 Resolution-External
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#7090
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?