Carl Morris

@JosKrause, have you a chance to look at PR #155? In that PR I have a more complete `class` and `enum` scoping. I could probably try to separate that out...

Noting PR #156 demonstrates this topic.

also see the images in this issue: https://github.com/PowerShell/vscode-powershell/issues/1401 It shows the static methods referenced in the first couple lines are colored wrong. Didn't realize it right away, as everything else...

Some more examples, ```PowerShell 1Dkb 1.Dkb 1.E12kb 1.1Dkb 1.1E12kb .1E+12Dkb 1Lkb 1.5Lpb 1.E12Lkb 1.14E12Lkb .14Ltb 1E12Lkb ``` I think there are a couple more scenario's included here, such as decimal...

> Commands/Functions, Variables, Parameters/Switches, methods/properties should each have their own individual color REGARDLESS of theme That's impossible. Its the theme that sets the color, and most themes are only based...

To include some shortcuts for reference: https://github.com/msftrncs/PowerShell.tmLanguage (VS Code ready JSON syntax file and some code samples, this is my primary work pad, changes occur here before they are committed...

I think I found a work-around for this: Change the 'end' matches for both 'interpolation' and 'interpolatedStringContent' to ``` "end": "(\\))((?:\\.(?:\\p{L}|\\d|_)+)*\\b)?", "endCaptures": { "1": { "name": "punctuation.section.group.end.powershell" }, "2": {...

also, this for both 'attribute' and 'type': ``` "end": "(\\])((?:\\.(?:\\p{L}|\\d|_)+)*\\b)?", "endCaptures": { "1": { "name": "punctuation.section.bracket.end.powershell" }, "2": { "name": "variable.other.member.powershell" } }, ```

Looks like I went too far with 'iterpolation' … it gets used by string expansion subexpressions, which causes problems with subexpressions in strings. This would need to get separated.

@omniomi, I'll try to work that up (relatively new to concept of Git). I can completely understand the goal of overhauling parts, as it becomes evident trying to trace down...