Dot notation broken inside parens.

[gerane]

This might be related to #14

It looks like just having a dot inside of parens breaks the Syntax Highlighting in the latest Insiders Preview 7/27

Sample Code:

if ($Host.name -eq 'ConsoleHost')
{
    if (! (Get-Item ENV:VSCODE_PID -ErrorAction SilentlyContinue))
    {
        ## Set Location
        Set-Location -Path Repo:
    }
}

This is how it is by default.

Removing the dot makes everything OK.

Just having a dot at end of Var breaks syntax highlighting.

This one is pretty bad, it breaks a quite a lot of the PowerShell I see. May have to manually load an old syntax.

Off Topic: What syntax highlight method does Github use? they seem to have decent results with PowerShell. Always been better than tmtheme overall.

[gravejester]

Yeah, I know what's causing this. It's the part trying to match the property of an object. I'm seeing too many issues with this, so I'm going to disable it entirely and push an update.

[vors]

@gerane GitHub uses current SublimeText bundle. https://github.com/github/linguist/tree/master/vendor/grammars

[omniomi]

Fixed by #94