You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Define a task that uses ${env:FOO} syntax to reference an existing environment variable.
Execute that task.
Observe that the expansion for that variable is an empty string.
The integrated terminal shows the expected env variable, so it's just the tasks.json that's affected (maybe other parts of VS Code too).
Does this issue occur when all extensions are disabled?: Yes (I checked this by creating a new Explorer shortcut to VS Code, with the disable option added to the commandline)
doxxx
changed the title
VS Code launched from Windows Explorer does not inherit all system environment variables
Environment variables expand to empty strings in tasks.json
Apr 11, 2019
Issue Type: Bug
${env:FOO}
syntax to reference an existing environment variable.The integrated terminal shows the expected env variable, so it's just the tasks.json that's affected (maybe other parts of VS Code too).
Does this issue occur when all extensions are disabled?: Yes (I checked this by creating a new Explorer shortcut to VS Code, with the disable option added to the commandline)
Example tasks.json
VS Code version: Code 1.33.0 (0dd516d, 2019-04-04T15:14:28.026Z)
OS version: Windows_NT x64 10.0.17134
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
Extensions (38)
The text was updated successfully, but these errors were encountered: