te

[xlebenny]

It's sound look like can set environment variables by "terminal.integrated.env.windows" config

• VSCode Version: 1.16.1
• OS Version: Windows 10

Steps to Reproduce:

1. File > Preference > Setting, save with below text
   {
   "terminal.integrated.env.windows": {
   "foo": "bar"
   }
   }

2. View > Integrated Terminal

3. input echo $foo in Terminal

Output:
Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\bar> echo $foo
PS C:\bar>

Expected Output:
Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\bar> echo $foo
bar <---- because configed in terminal.integrated.env.windows
PS C:\bar>

Reproduces without extensions: Yes

[alexdima]

@xlebenny Can you please write steps for your problem ?

[xlebenny]

Updated @alexandrudima , but which setting trigger stackovewflow copy my post to here?

[yume-chan]

In PowerShell, $foo means a local variable named foo, and $env:foo means an environment variable named foo.

I have confirmed that echo $env:foo does work.

[xlebenny]

@yume-chan i tried below is work for me

"terminal.integrated.env.windows": {
    "foo": "bar"
}

PS C:\bar> echo $env:foo
bar

but, how to append variable instead of replace?

"terminal.integrated.env.windows": {
    "path": "$Env:Path;C:\\new\\path"
}

PS C:\bar> echo $Env:Path
$Env:Path;C:\new\path

[yume-chan]

See #34337. There is currently no way to do that.

${env:Name} is supported in tasks.json, can it be extended to settings.json? @Tyriar

EDIT: I also found #32273 that's a feature request.

[Tyriar]

Closing as duplicate of #34337

@yume-chan I'll reopen the issue with syntax similar to tasks.