Carl Morris

Would the error of 'look-behind contains non-fixed length expression' get forwarded when the engine catches the error? That's the error I would get when I would attempt to use a...

@rjmholt, I think #8028 has been completed and closed now as of PS Core 6.2.

PowerShell only treats `@` as a special symbol if it is the first character of a token (and even then there are additional rules that can reject its special treatment...

For those interested, I've been working on completion escaping issues that are internal to PowerShell, and put together the following gist for demonstrating the escaping of an argument completion: https://gist.github.com/msftrncs/bff8c6c5e28ff92a19efb8a5556a4238

> EditorSyntax is no longer used in VS Code when you have the PowerShell extension installed. Incorrect. Unless your theme is marked as supporting semantic highlighting, you will 100% use...

@rjmholt, that doesn't sound correct. That doesn't sound like a smart thing to do, to not be able to use a new API because you must still support an old...

GitHub works fine if you fence the code... Source: ```md | Option | Description | | ------ | ----------- | | data | path to data files to supply the...

This is handled in PR #156. 

There are a few issue remaining: - [x] `in` keyword of `foreach` not handled - [x] `else` or `elseif` not handled if used on same line as the `if` -...

A JSON version of the syntax is available at https://github.com/msftrncs/PowerShell.tmLanguage/tree/argumentmode_2ndtry, I produced this PList version from there,