Patrick Meinecke

@gerardog You may want to explicitly define how you would like vulnerabilities to be disclosed. I could be missing it, but I only see how you would like positive analysis...

Looks like a problem with the dotnet global tool install of PowerShell. Unsure if it's us or if the way args are passed to it is a little wonky on...

@compwiz32 This looks sort of similar to when something is blocking `nodepty.exe`. Are you able to specify which anti-virus you are using? I know someone reported needing to white list...

(I'm about to explain some things, but I don't think this should be closed. I don't know of a good way to fix it off the top of my head...

Issue is we get all of our intellisense directly from PowerShell (`SMA.CommandCompletion.CompleteInput` method). So if we want to do something different than what PowerShell does already, we have to reimplement...

Adding onto @rkeithhill's example: ```powershell & { $foo = 'test' } . { $foo = 'test' } & { $foo } 0..10 | ForEach-Object { $foo } 0..10 | Where-Object...

@rjmholt Definitely agree that it would be useful. It's hard to guess what the ratio of confusion/frustration to benefit will be though. Most users won't understand the reason why some...

I think most of the stuff you're looking for in `$psEditor` is probably under `$psEditor.GetEditorContext()` e.g. to set the cursor location to line 30 column 10 you can do ```powershell...

> @andschwa I think this is because the F8 takes a different code path, can we still run it through psreadline somehow for the output? Yeah we just write it...

Yep! Been like that since PSRL integration was added (well before that too since we didn't have syntax highlighting at all before then).