Syntax highlighter crasehes after typing subexpression within Write-Host cmd

[1RedOne]

Issue Description

Syntax highlighter reports everything as error when typing a $SubExpression.

Attached Logs

sent via email
Follow the instructions in the README about
capturing and sending logs.

Environment Information

Visual Studio Code

Name	Version
Operating System	Windows_NT x64 10.0.14393
VSCode	1.20.1
PowerShell Extension Version	1.6.0

PowerShell Information

Name	Value
PSVersion	5.1.14393.2068
PSEdition	Desktop
PSCompatibleVersions	1.0 2.0 3.0 4.0 5.0 5.1.14393.2068
BuildVersion	10.0.14393.2068
CLRVersion	4.0.30319.42000
WSManStackVersion	3.0
PSRemotingProtocolVersion	2.3
SerializationVersion	1.1.0.1

Visual Studio Code Extensions

Visual Studio Code Extensions(Click to Expand)

Extension	Author	Version
bracket-pair-colorizer	CoenraadS	1.0.20
git-indicators	lamartire	2.1.1
gitlens	eamodio	8.1.1
hopscotch	idleberg	0.2.2
nord-visual-studio-code	arcticicestudio	0.6.0
PowerShell	ms-vscode	1.6.0
theme-glacier	Kal	0.0.1

[1RedOne]

I mean, I know that I should avoid Write-host, but I didn't think it would crash VSCode Syntax Highlighter.

[rkeithhill]

What exactly do you mean by crashing? Does the language server actually crash? If so, can you please provide the log files for that session (see https://github.com/PowerShell/vscode-powershell#reporting-problems for instructions on attaching a zip of the log files). Or do you see that syntax colorization is messed up after this command?

[rjmholt]

If you have an error trace for a crash like this, that would very helpful

[TylerLeonhardt]

I think I understand what @1RedOne is saying and I think it's a dupe of #1232.

My guess is syntax highlighter is PSSA results (aka squiggles 👍 ).

[1RedOne]

Hi guys! I emailed the error logs in as requested, and by crashing I mean that red-squiggles appear under everything and that syntax highlighting no longer works. I've had a few repros since then, and it looks like it happens a lot when dealing with here-strings of multi line hashtables.

…

On Sun, Mar 25, 2018 at 10:27 AM, Tyler James Leonhardt < ***@***.***> wrote: I think I understand what @1RedOne <https://github.com/1RedOne> is saying and I think it's a dupe of #1232 <#1232>. My guess is syntax highlighter is PSSA results (aka squiggles 👍 ). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1229 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABMJilCvwzo0FzISQo_DFhpcjc6oIrsdks5th6lFgaJpZM4Ssn-W> .

[TylerLeonhardt]

Hmm I don't think I got the email. You sent it to: [email protected]?

[TylerLeonhardt]

Alternatively you can upload the zip here so more eyes can debug 😄 lots of awesome non-Microsoft maintainers 😄

[TylerLeonhardt]

I don't think I ever got your email... :(

The squiggles are due to PSScriptAnalyzer and if you're receiving those when you shouldn't be, it's better to open an issue here: https://github.com/PowerShell/PSScriptAnalyzer

If it's related to general slowness of the extension not updating squiggles that's tracked with #1232

And if syntax highlighting is breaking for some reason, you'll want to open an issue on:
https://github.com/powershell/editorsyntax

I'm going to close this as both a mix of a dupe of 1232 and an external issue. If you see otherwise, let me know and I'm more than happy to reopen :)