environment variable substitution not working in tasks.json

[britt]

• VSCode Version: 1.13.0
• OS Version: macOS Sierra 10.12.5

Steps to Reproduce:

1. Update to 1.13.0
2. Quit VSCode
3. Open VSCode
4. Run a task where the command relies on env var substitution like "command": "${env.GOPATH}/bin/gnatsd",

Results:

execvp(3) failed.: No such file or directory
The terminal process terminated with exit code: 1

Terminal will be reused by tasks, press any key to close it.

Specifying a complete path to the executable works, but any path that relies on ${env.*} fails.

[britt]

I checked and other variable substitutions like workspaceRoot still work. It is only env that fails.

[rkeithhill]

I'm seeing the same thing with ${env.windir} in 1.13.0. Used to work but no longer. Here's the relevant part of my tasks.json:

    // Start PowerShell
    "windows": {
        "command": "${env.windir}\\sysnative\\WindowsPowerShell\\v1.0\\powershell.exe",
        "args": [ "-NoProfile", "-ExecutionPolicy", "Bypass" ]
    },

The same task works fine if I substitute C:\\Windows for ${env.windir}.

[TheBurnDoc]

Same problem in launch.json ${env.USERPROFILE} no longer works in windows

[triztian]

Not sure how to link issues but this is a dupe: #28533

[ucirello]

if I may add, this is a daily nuisance. IMHO, worth a recovery release.

[dbaeumer]

This happened as a side effect of fixing
#16064. In debug land there was confusion between using '.' and ':' as a separator so we decided to use ':' as a separator for the scope. Since debug and task share the same variable resolving mechanism this got changed for tasks without a necessary deprecation warning.

So the new syntax is ${env:GOPATH} or `${env:windir}. We will look into adding a deprecation warning for this.

Sorry for the breakage.

[triztian]

The docs should be updated to reflect that update.

• https://code.visualstudio.com/Docs/editor/tasks#_variable-substitution

[TheBurnDoc]

Thanks!

[dbaeumer]

@gregvanl can you please update the doc for 1.13. This slipped through my cracks. The debug documentation might need some updating as well.

[gregvanl]

Documentation fixed with microsoft/vscode-docs@6c11a91