${env:path} not evaluted in "terminal.integrated.env.windows" if ${workspaceFolder} doesn’t exist #233495
Labels
bug
Issue identified by VS Code Team member as probable bug
confirmation-pending
terminal-process
Problems launching processes, managing ptys, exiting, process leaks, etc.
Milestone
Does this issue occur when all extensions are disabled?: Yes/No
Steps to Reproduce:
Using this settings when opening VSCode with no folder opened in it.
will result:
because
${workspaceFolder}
doesn’t exist.Using something like
"PATH": "c:\\any\\other\\path\\bin;${env:PATH}"
will work fine.Suggestion
If
${workspaceFolder}
can not be evaluated, pass it as a string and continue to try to evaluate other variables in"PATH"
.The text was updated successfully, but these errors were encountered: