Patrick Meinecke

Yep it's on my list but I haven't actually done anything to fix it yet. I was initially thinking it wouldn't be a blocker but this might make debugging pester...

When that happens, can you type `list` in the extension terminal? See where PowerShell itself thinks we've hit a sequence point?

Talked this over a bit in discord. Looks like we are setting cursor position *but not* moving to the next file. So either our call to switch to the file...

Note this is "signature help" rather than a code lens but yeah it'd be nice for sure. It'd need a call to `StaticParameterBinder.BindCommand` which is pretty expensive, so it may...

Ideally one day we'd just be able to sync breakpoints outside of debug sessions. Dunno if that day will ever come, but it sure would be ideal if "interactive debugging"...

I'm unsure if that makes sense for general completions tbh It does however seem like a good way to hook up predictions if we ever find a compelling scenario.

I'm gonna quote a [comment I wrote awhile ago](https://github.com/PowerShell/PowerShellEditorServices/issues/701#issuecomment-406795269) about this: > That error is expected when debugging a script where a frame in the call stack is within a...

> FWIW, I see these errors get added to $Global:Error every time I F10 in vscode debugger. > > @SeeminglyScience wrote: > > > I typically only advise $Error to...

Fixing this is a little bit more difficult than it may appear. The big problem with this one is that it's basically impossible to set the `PSScriptRoot` variable manually because...

> Hm, that's odd. I thought we were always dot-sourcing scripts. In fact, there was a regression where we changed to using the ampersand call-operator and had to change it...