Carl Morris

This is how the code should have appeared with PR 156:  Note it marks the backticks 'invalid' as they will not do anything, but they do not generate an...

Clarification, the current grammar is behaving correctly, PR #156 would have caused a regression, and a recent commit has resolved that, as shown in the image in https://github.com/PowerShell/EditorSyntax/issues/161#issuecomment-470231962.

A quick correction, (noting that static members are allowed here too). (I might be using a different scope for the member here than the regular syntax is using) For the...

Add scriptblocks to the list of items that should have member access scoped, not a common item by any means, as I am not sure it has any practical uses...

Is there anything wrong with using multiple scopes? I was doing some testing with VS Code, applying both scopes, and its a nice improvement to get intellisense inside the subexpressions....

I got the best result actually putting 'meta.embedded' on "name" of the pattern rather than "contentName". Dark+, Monokai, and Monokai Dimmed all started coloring subexpressions within strings correctly, including the...

I plan to post a PR per my previous comment. Does anyone know where the `interpolated.complex` scope came from?

looking at #129, I have to disagree that the changes are all bad, though some changes were unexpected, the changes are making some things more like PowerShell ISE, while somethings...

Technically negative numeric constants as an argument are considered unquoted text by the PS tokenizer (as indicated by PSReadLine highlighting). So the TextMate scope is wrong. But the sematic highlighter...

Actually, I give a bad example with 'echo' (`Write-Output`) because the output processor (formatter) just provides the original text behind the argument, so: ```PowerShell echo 0006 ``` results in ```...