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

Color Escape codes not working in MSYS (Git Bash) #4821

New Issue
Closed
opened 2026-01-30 23:57:25 +00:00 by claunia · 6 comments
claunia commented 2026-01-30 23:57:25 +00:00
Owner
Copy Link

Originally created by @benjamw on GitHub (Nov 5, 2019).

Environment

Windows build number: 
- Microsoft Windows [Version 10.0.18362.418]

Windows Terminal version (if applicable): 
- Windows Terminal (Preview)
- Version: 0.6.2951.0

Any other software?
- Git Bash for Windows (MINGW64)
- Ubuntu (WSL)

Steps to reproduce

Open a Git Bash tab in Windows Terminal.
Run the following script:

#!/bin/bash

# This program is free software. It comes without any warranty, to
# the extent permitted by applicable law. You can redistribute it
# and/or modify it under the terms of the Do What The Fuck You Want
# To Public License, Version 2, as published by Sam Hocevar. See
# http://sam.zoy.org/wtfpl/COPYING for more details.

for fgbg in 38 48 ; do # Foreground / Background
    for color in {0..255} ; do # Colors
        # Display the color
        printf "\e[${fgbg};5;%sm  %3s  \e[0m" $color $color
        # Display 6 colors per lines
        if [ $((($color + 1) % 6)) == 4 ] ; then
            echo # New line
        fi
    done
    echo # New line
done

exit 0

Expected behavior

Pretty colors.

Actual behavior

Only a small number of colors.

An image is attached that shows Git Bash running that script, then Git Bash in Windows Terminal running that script, and finally Ubuntu in Windows Terminal running that script.

Git Bash shows the colors as expected, as does Ubuntu in Windows Terminal, so it seems reasonable that both Git Bash, and Windows Terminal support those colors, but somewhere between them, the colors get mangled and do not show properly.

Image3

Originally created by @benjamw on GitHub (Nov 5, 2019). # Environment ```none Windows build number: - Microsoft Windows [Version 10.0.18362.418] Windows Terminal version (if applicable): - Windows Terminal (Preview) - Version: 0.6.2951.0 Any other software? - Git Bash for Windows (MINGW64) - Ubuntu (WSL) ``` # Steps to reproduce Open a Git Bash tab in Windows Terminal. Run the following script: ```bash #!/bin/bash # This program is free software. It comes without any warranty, to # the extent permitted by applicable law. You can redistribute it # and/or modify it under the terms of the Do What The Fuck You Want # To Public License, Version 2, as published by Sam Hocevar. See # http://sam.zoy.org/wtfpl/COPYING for more details. for fgbg in 38 48 ; do # Foreground / Background for color in {0..255} ; do # Colors # Display the color printf "\e[${fgbg};5;%sm %3s \e[0m" $color $color # Display 6 colors per lines if [ $((($color + 1) % 6)) == 4 ] ; then echo # New line fi done echo # New line done exit 0 ``` # Expected behavior Pretty colors. # Actual behavior Only a small number of colors. An image is attached that shows Git Bash running that script, then Git Bash in Windows Terminal running that script, and finally Ubuntu in Windows Terminal running that script. Git Bash shows the colors as expected, as does Ubuntu in Windows Terminal, so it seems reasonable that both Git Bash, and Windows Terminal support those colors, but somewhere between them, the colors get mangled and do not show properly. ![Image3](https://user-images.githubusercontent.com/186505/68230447-48155880-ffb6-11e9-8a14-25e6f62d5b2f.png)
claunia commented 2026-01-30 23:57:26 +00:00
Author
Owner
Copy Link

@Biswa96 commented on GitHub (Nov 5, 2019):

What command did you run to open msys2 bash in Windows Terminal?

@Biswa96 commented on GitHub (Nov 5, 2019): What command did you run to open msys2 bash in Windows Terminal?
claunia commented 2026-01-30 23:57:26 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 5, 2019):

It's very suspicious that 7 had the color reversed, 30-37 had the foreground colors set to what you'd expect from ^[[31m-^[[37m, and the same with the backgrounds for 41-47.

What's TERM set to in the git bash shell running in Windows Terminal?

@zadjii-msft commented on GitHub (Nov 5, 2019): It's very suspicious that `7` had the color reversed, 30-37 had the foreground colors set to what you'd expect from `^[[31m`-`^[[37m`, and the same with the backgrounds for 41-47. What's `TERM` set to in the git bash shell running in Windows Terminal?
claunia commented 2026-01-30 23:57:26 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 5, 2019):

I'm rather certain this is the same root cause as #2837, which makes it firmly an external bug. Msys2's runtime is derived from Cygwin's.

I've debugged through conhost, and it looks like they're never sending us even a single escape sequence -- they're iterating through and calling SetConsoleTextAttribute, WriteConsole, SetConsole... where they try to change the attribute every time.

More info here: https://github.com/microsoft/terminal/issues/2837#issuecomment-533830745

@DHowett-MSFT commented on GitHub (Nov 5, 2019): I'm rather certain this is the same root cause as #2837, which makes it firmly an external bug. Msys2's runtime is derived from Cygwin's. I've debugged through conhost, and it looks like they're never sending us even a single escape sequence -- they're iterating through and calling `SetConsoleTextAttribute`, `WriteConsole`, `SetConsole...` where they try to change the attribute every time. More info here: https://github.com/microsoft/terminal/issues/2837#issuecomment-533830745
claunia commented 2026-01-30 23:57:26 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 5, 2019):

Incidentally, it looks like Cygwin upstream added support for passing through color sequences to the console host 7 month ago. Judging by the version Git for Windows ingested, they're a year out-of-date. The copyright indicates "20xx-2018".

@DHowett-MSFT commented on GitHub (Nov 5, 2019): Incidentally, it looks like Cygwin upstream added support for passing through color sequences to the console host 7 month ago. Judging by the version Git for Windows ingested, they're a year out-of-date. The copyright indicates "20xx-2018".
claunia commented 2026-01-30 23:57:26 +00:00
Author
Owner
Copy Link

@benjamw commented on GitHub (Nov 5, 2019):

Thanks for the info. Sorry for the duplicate issue.

@benjamw commented on GitHub (Nov 5, 2019): Thanks for the info. Sorry for the duplicate issue.
claunia commented 2026-01-30 23:57:27 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 6, 2019):

@benjamw no problem! It's hard to find these things out, and the one in question was already closed. Sorry about the lack of discoverability 😄

@DHowett-MSFT commented on GitHub (Nov 6, 2019): @benjamw no problem! It's hard to find these things out, and the one in question was already closed. Sorry about the lack of discoverability :smile:
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 Area-VT Issue-Question Needs-Attention Needs-Triage Product-Terminal 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#4821
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?