GVM does not function correctly in WSL

[orhpeus]

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:

[andot]

I fix it in this pr: https://github.com/moovweb/gvm/pull/443

[bamaas]

Also facing this issue over here. Tried your fix @andot but still facing the same problem.

[orhpeus]

I temporarily used the following method to disable the resolution of Windows paths.

1. Create a new /etc/wsl.conf configuration file under wsl and edit the following:

[interop] appendWindowsPath=false

[ankitcharolia]

@andot @orhpeus @bamaas kindly try this out. I am using this goenv: https://github.com/ankitcharolia/goenv.

[k0b3rIT]

I am facing the same issue on an ARM MAC with zsh.

[k0b3rIT]

@andot 's solution solves the problem THX!

[goFrendiAsgard]

For anyone who comes here because of this problem: @andot PR has been there since September 2023, and I don't think the maintainer (@moovops) will merge the PR in the near time.

You can always rollback to the point when the defect has not been introduced, or you can add this at the end of your ~/.zshrc or ~/.bashrc

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.