Skip to content

Conversation

@rkeithhill
Copy link
Contributor

We used to have ${env.windir} but then VSCode broke us so we switched back to C:\Windows.

It turns out that the VSCode folks changed the syntax to ${env:windir} - replacing the dot with a colon.

Here's the VSCode issue describing this: microsoft/vscode#28365 (comment)

We used to have ${env.windir} but then VSCode broke us so we switched back to C:\Windows.

It turns out that the VSCode folks changed the syntax to ${env:windir} - replacing the dot with a colon.

Here's the VSCode issue describing this: microsoft/vscode#28365 (comment)
@daviwil
Copy link
Contributor

daviwil commented Jun 17, 2017

Ahhh, fantastic, thanks for looking into that!

@daviwil daviwil added this to the June 2017 milestone Jun 17, 2017
@daviwil daviwil merged commit ab4b4c2 into master Jun 17, 2017
@daviwil daviwil deleted the rkeithhill/use-env-windir branch June 17, 2017 17:22
@daviwil daviwil modified the milestones: June 2017, 1.4.0 Jun 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants