-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
'$HOME/.wsl-cmds' not in path when starting vscode normally #27
Comments
please redownload the |
Sorry, I completely got that wrong. I don't know my own code it seems. the |
When starting vscode without launching it from a WSL shell with
remote.WSL.useShellEnvironment
enabled,$HOME/.wsl-cmds
will not be available in path.Making both the SSH and the GPG agent inaccessible to vscode and other tools that take the same approach as vscode to detect the environment.
Maybe it is an idea to make the script add
PATH="$HOME/.wsl-cmds:$PATH:/snap/bin"
to~/.bashrc
,~/.profile
or whatever vscode gets the environment from? Or maybe it's an idea to change how the environment is configured?Without it will make both the forwarded agents and snap inaccessible from vscode as snap is also not in path.
The text was updated successfully, but these errors were encountered: