IssueRaiser

Use fresh environment block on new terminals in Windows

At the moment, if any environment variables change, or new "apps" are installed while VS Code is running, in order for those changes to be recognized VS Code needs to be closed and re-open. For instance, when running `npm i -g <something>` or `choco install <package>` in another prompt or powershell window, those new commands are not recognized until the app is rebooted. It would be great if adding a new terminal instance with `+` would load these new variables/apps/notsurewhatterminologytouse.

Posted by eslachance on Apr 13, 2018, 9:07 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments

onboarding (SaaS)

Use fresh environment block on new terminals in Windows

eslachanceApr 13, 2018, 9:07 AM

At the moment, if any environment variables change, or new "apps" are installed while VS Code is running, in order for those changes to be recognized VS Code needs to be closed and re-open. For instance, when running `npm i -g <something>` or `choco install <package>` in another prompt or powershell window, those new commands are not recognized until the app is rebooted. It would be great if adding a new terminal instance with `+` would load these new variables/apps/notsurewhatterminologytouse.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue