Incorrect output when using Git for Windows bash.exe profile #6591

Open
opened 2026-01-31 00:42:29 +00:00 by claunia · 0 comments
Owner

Originally created by @benjivm on GitHub (Feb 22, 2020).

Environment

Windows build number: 10.0.18363.0 Microsoft Windows NT 10.0.18363.0
Windows Terminal version (if applicable): 0.9.433.0

Steps to reproduce

Use the following (or similar, i.e., bash.exe) profile:

"profiles" : 
[
    {
        "name" : "bash",
        "guid": "{00000000-0000-0000-ba54-000000000001}",
        "closeOnExit" : true,
        "colorScheme" : "One Half Dark",
        "fontFace" : "Cascadia Mono PL",
        "fontSize" : 12,
        "commandline" : "\"%USERPROFILE%\\scoop\\apps\\git\\current\\bin\\bash.exe\" -i -l",
        "icon" : "%USERPROFILE%\\scoop\\apps\\git\\current\\mingw64\\share\\git\\git-for-windows.ico",
        "useAcrylic" : true,
        "startingDirectory" : "%USERPROFILE%",
        "acrylicOpacity" : 0.8
    },
]

Expected behavior (top, git-bash.exe) Actual behavior (bottom, wt.exe with above profile)

Expected behavior (top, git-bash.exe) Actual behavior (bottom, wt.exe with above profile)

Originally created by @benjivm on GitHub (Feb 22, 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 ```none Windows build number: 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 Windows Terminal version (if applicable): 0.9.433.0 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Use the following (or similar, i.e., `bash.exe`) profile: ```json "profiles" : [ { "name" : "bash", "guid": "{00000000-0000-0000-ba54-000000000001}", "closeOnExit" : true, "colorScheme" : "One Half Dark", "fontFace" : "Cascadia Mono PL", "fontSize" : 12, "commandline" : "\"%USERPROFILE%\\scoop\\apps\\git\\current\\bin\\bash.exe\" -i -l", "icon" : "%USERPROFILE%\\scoop\\apps\\git\\current\\mingw64\\share\\git\\git-for-windows.ico", "useAcrylic" : true, "startingDirectory" : "%USERPROFILE%", "acrylicOpacity" : 0.8 }, ] ``` # Expected behavior (top, `git-bash.exe`) Actual behavior (bottom, `wt.exe` with above profile) ![](https://i.imgur.com/oldWzzj.png) # Expected behavior (top, `git-bash.exe`) Actual behavior (bottom, `wt.exe` with above profile) ![](https://i.imgur.com/BARMOBg.png)
claunia added the Needs-Tag-FixNeeds-Attention labels 2026-01-31 00:42:29 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6591