Semantic Syntax is incorrectly highlighting arguments as commands

Any bare (unquoted) string argument that has a - in it is being highlighted as a command:

[TylerLeonhardt]

So I think we need to take this in two stages.

1. The first stage is parity: being as close to PSReadLine as possible. This will allow both the console and editing experience to be on the same playing field. (this was actually the original goal of doing this work from the beginning)

2. The second stage is improving: Once both experiences are roughly aligned, then we can go back and make the changes in both to support the language better.

[SeeminglyScience]

@rjmholt I think what they’re getting at is that the current regex based highlighter treats the name in a function definition like a command (which doesn’t have the flag).

Personally I’d rather have the name in a function definition be parsed as a bare word than the current situation (that’s how both the ISE and PSRL work currently). But a fix for both might be just keeping track of if the previous token kind was Function. Then also use TokenFlags.CommandName.