-
Notifications
You must be signed in to change notification settings - Fork 8.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Git-bash ansi/vt100 #4809
Comments
I'm fairly sure this is the same root cause as #2837 (comment) (the cygwin/msys2 runtime (which are pretty much the same code) isn't acting the same as it would in standard conhost, even though WT goes to great lengths to ensure that conhost things work as well as possible.) Would you mind sharing the output of Additionally, would you mind sharing your git-bash profile snippet (from profiles.json)? |
(Tentative dupe ruling stands until more info comes in; closing) |
both inside and outside WT, but in git-bash,
|
@DHowett-MSFT I've just managed to fix the problem by recompiling Git for windows using Cygwin 3.1.2 and essentially replacing the msys-2.0.dll (it is essentially the cygwin1.dll) binary - it works perfectly now! |
FWIW this was reported for |
Hi @DHowett-MSFT, According to the git-gui developer, @prati0100, this is a Windows Terminal issue, and not a git-gui issue. I don't think my issue is related to #2837 (comment), as I am using PowerShell 6 and not cygwin/msys2. I am also not sure whether my issue is related to this issue which seems to be about git-bash, and I am using pwsh. @DHowett-MSFT can you re-open this issue, or am I having a different bug and should I open a new issue? Thanks a lot. |
Hey @patrikhuber! What you’re seeing is definitely different from this issue; mind filing a separate one? I’ve seen some unusual behavior with git-gui where launching it (a graphical application) resets the output handle to not process VT until the shell steps in and fixes it, but I haven’t grabbed console host traces to see what exactly is happening. |
(Incidentally: when I say it’s a Cygwin issue, it may still apply to git-gui even if you’re not knowingly using Cygwin. The runtime that it uses for being POSIXy cross-platform is derived from (or in some cases directly built from) Cygwin’s standard library 😄) |
@DHowett-MSFT Sure! I've opened #4921. Thanks a lot for the quick reply! (Ah I think I see what you mean. Git-gui probably uses Cygwin/msys2, so this might be related even though I am using PowerShell and not git-bash.) |
@molszews can you create a PR for https://github.com/git-for-windows/git that upgrades the libraries? Maybe that would get the ball rolling? |
Environment
Steps to reproduce
stern
Expected behavior
Actual behavior
Comments
There are similar issues already here tracked, however, I'm not 100% sure if this is the same case (cygwin related issue #2837), as starting git-bash and running apps there works fine:
Problem is when the same git-bash is now started via Windows Terminal,
The text was updated successfully, but these errors were encountered: