-
Notifications
You must be signed in to change notification settings - Fork 556
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
GVM does not function correctly in WSL #445
Comments
I fix it in this pr: #443 |
Also facing this issue over here. Tried your fix @andot but still facing the same problem. |
I temporarily used the following method to disable the resolution of Windows paths.
[interop] |
@andot @orhpeus @bamaas kindly try this out. I am using this goenv: https://github.com/ankitcharolia/goenv. |
I am facing the same issue on an ARM MAC with zsh. |
@andot 's solution solves the problem THX! |
For anyone who comes here because of this problem: You can always rollback to the point when the defect has not been introduced, or you can add this at the end of your export PATH=$(echo $PATH | sed 's/:\([^/]\)/ \1/g') This workaround simply looks for any colon character that is not followed by a slash and replaces it with a space. |
I am using gvm under WSL2. When the following script was added to the .bashrc,
[[ -s "/home/m2m/.gvm/scripts/gvm" ]] && source "/home/m2m/.gvm/scripts/gvm"
I noticed that VS Code did not start properly.
After looking at $PATH, it is found that the spaces in the path become colons.
As shown in the following figure:
When GVM disabled:
When GVM enabled:
The text was updated successfully, but these errors were encountered: