-
Notifications
You must be signed in to change notification settings - Fork 38.2k
Closed
Closed
Copy link
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buginsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsiderslinuxIssues with VS Code on LinuxIssues with VS Code on LinuxmacosIssues with VS Code on MAC/OS XIssues with VS Code on MAC/OS XverifiedVerification succeededVerification succeededworkbench-cliVS Code Command line issuesVS Code Command line issues
Milestone
Description
- VSCode Version: 1.25.1
- OS Version: Ubuntu 16.04.5 x86_64 (This is Linux and macOS only)
Steps to Reproduce:
- Open VS Code from the GUI (.desktop shortcut) (
VSCODE_CLIwill be unset) - Open a separate terminal window and change your
PATH, for example: Enter avirtualenv. - Launch VS Code from that terminal:
code .. - Open the developer tools and check
process.env. YourPATHwill be reset to your shell's default.
The cause is that this code: https://github.com/Microsoft/vscode/blob/d983257e6f8db693962d0dba9a025678f50778fe/src/vs/code/node/shellEnv.ts#L83-L92
Is executed in the VS Code main process that gets it's environment variables from the first launch of VS Code instead of checking if the new environment that was received for this launch request is from the GUI or CLI.
Does this issue occur when all extensions are disabled?: Yes
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buginsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsiderslinuxIssues with VS Code on LinuxIssues with VS Code on LinuxmacosIssues with VS Code on MAC/OS XIssues with VS Code on MAC/OS XverifiedVerification succeededVerification succeededworkbench-cliVS Code Command line issuesVS Code Command line issues