We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have followed the instructions here for Windows Terminal: https://www.msys2.org/docs/terminals/
As such the command line is: C:/msys64/msys2_shell.cmd -defterm -here -no-start -use-full-path -mingw64
C:/msys64/msys2_shell.cmd -defterm -here -no-start -use-full-path -mingw64
However this causes the issue network paths don't open properly:
There are various ways I thought of working around this:
C:/msys64/msys2_shell.cmd
The best way so far seems to be instead using:
C:\msys64\usr\bin\env.exe MSYSTEM=MINGW64 CHERE_INVOKING=1 /usr/bin/bash.exe --login
This works fine:
The text was updated successfully, but these errors were encountered:
For inheriting the PATH, this worked for me instead:
PATH
C:/tools/msys64/usr/bin/bash.exe -c "MSYS2_PATH_TYPE=inherit MSYSTEM=MINGW64 CHERE_INVOKING=1 exec /usr/bin/bash.exe --login"
Sorry, something went wrong.
No branches or pull requests
I have followed the instructions here for Windows Terminal: https://www.msys2.org/docs/terminals/
As such the command line is:
C:/msys64/msys2_shell.cmd -defterm -here -no-start -use-full-path -mingw64
However this causes the issue network paths don't open properly:
There are various ways I thought of working around this:
C:/msys64/msys2_shell.cmd
script with a Powershell instead of CMD scriptThe best way so far seems to be instead using:
This works fine:
The text was updated successfully, but these errors were encountered: