Windows Terminal instructions don't work with network paths
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 3.3k
- Forks
- 446
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 1
Description
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:
- Replace the
C:/msys64/msys2_shell.cmdscript with a Powershell instead of CMD script - Invoke bash.exe directly from Windows Terminal, however this will require setting environment variables which is currently not directly supported https://github.com/microsoft/terminal/issues/2785
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:

Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Windows Terminal instructions at https://www.msys2.org/docs/terminals/ and compare the documented msys2_shell.cmd command with the working env.exe and bash.exe command in the issue. Reproduce the network-path behavior, then update the instructions to provide a working command or clearly documented workaround and verify that network paths open correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, shell
- Domain
- cli, documentation
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100