When I do ‘Get Bash Here’ on a network location the console isn’t in that directory. Instead the directory is /c/Windows.
Is this a limitation of Git Bash?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When I do ‘Get Bash Here’ on a network location the console isn’t in that directory. Instead the directory is /c/Windows.
Is this a limitation of Git Bash?
No, this is a limitation of Windows. The Windows “current directory” for a program cannot be UNC pathname, but must be a path with a drive letter. You will need to assign a drive letter to your network location.
You can either do this through the normal Windows Explorer method, or there’s a shortcut command line to automatically create a drive letter:
Run that in a usual Windows
cmdshell, and it will allocate a new drive letter and change to it. Then you can use “Git Bash Here” on that drive letter and path from Windows Explorer.