Bug fixes. Should fix:

[gravejester]

#9

#10

#11

[msftclas]

Hi @gravejester, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!

The agreement was validated by Microsoft and real humans are currently evaluating your PR.

TTYL, MSBOT;

[gerane]

Nice!

[gravejester]

@gerane Turned out two of the issues were related, so easy fix :)

Thanks for testing and finding these bugs btw!

[gerane]

No problem. I should just be able to copy the TM language into code to try these changes out shouldn't I?

I use code as my daily driver, and I have always liked themes, so I will be paying closer attention for anything off.

[gravejester]

Yes, just copy the language file over the existing one, and restart code.

[daviwil]

Thanks man! I'll take a look at this later today when I'm back in Athens.

[daviwil]

@gerane, did the fixes resolve the issues for you when you tried it?

[daviwil]

Hmmm, was this necessary to get VS Code to operate correctly? I wonder if it'd have a negative effect on other editors?

[gravejester]

Ah.. that was just a visual help for me when working with the definitions in Sublime Text, as I had two versions of the language files installed :) I'll revert it back.

[gerane]

I haven't tried it yet. Got caught up in a bug in a vendor's product at work. So I've wasted the last couple days dealing with foreign support I can barely understand. They blamed Microsoft like usual, even though I can't even begin to see how it is related to Microsoft. I think that is just their go to answer.

[CodeCyclone]

I tested this out and it worked for me by updating "C:\Program Files (x86)\Microsoft VS Code\resources\app\extensions\powershell\syntaxes\PowershellSyntax.tmLanguage"

[daviwil]

Hey @gravejester, sorry for the delay on getting this merged. Done now!

By the way, the VS Code team gave me write access to their repo so I should be able to approve your PRs there now ;)

[ftischhauser]

I'm still seeing some color coding issues even after replacing this file manually:

Example 1:

$email = "[email protected]"

Example 2:

$XML = @"
<?xml version="1.0" encoding="UTF-16"?>
    <test>powershell.exe -Command "&amp; {if($var.'$name'){Write-Output 'hello world'}}"</test>
"@
Write-Output 'hello world'

Both work perfectly with VSCode 1.2.1 and vscode-powershell 0.6.1.

Thanks for looking into this :)