-
Notifications
You must be signed in to change notification settings - Fork 167
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
Version 0.4.3 that comes with git bash 2.14.1 cannot execute cmd.exe #127
Comments
The problem reproduces in MSYS2 without the Git-for-Windows packaging. The root cause is this MSYS2 patch which uses backslashes instead of forward slashes. Maybe the fix for #81 / #98 probably contributes to the issue by making winpty use absolute paths more often. With the MSYS2 patch, winpty-agent.exe runs
Upstream winpty should use MSYS2's special path conversion somehow, but AFAIK, there's no public API for it exposed from |
Related to #88. |
Hello Richard, what needs to be done to fix this? Do you need some help with this? |
Any progress? |
+1 |
As pointed by msys2/MSYS2-packages#411 (comment) , I managed to fix this issue by not installing the package from the msys2 repository (i.e.,
Now it correctly opens |
This was tested on windows 7 pro with latest updates.
Every time I type
winpty cmd.exe
in git bash prompt, it will exit immediately with no error message. I also notice that it creates an.exe
subdirectory in the current directory, because after the secondwinpty cmd.exe
it reports an error: "A subdirectory or file .exe already exists"Other commands such as python.exe/node.exe/powershell.exe seem to work fine.
The text was updated successfully, but these errors were encountered: