Patrick Meinecke

> If we defer entering the debugger for unhandled exceptions until such a time that we know the exception is considered unhandled, where are we in our call stack? We...

@KirkMunro do you know if there's a way to only break on uncaught errors? Or otherwise determine that an error was uncaught? Also determine whether the error was terminating? Right...

@JustinGrote Yeah for sure, there's still great value in enabling "All Exceptions".

> It will still be a behavior change though, as all the output of the script block will be written out to the console. So for any existing script block...

If it's determined to be the responsibility of the handler writer, they could just pipe to `Out-Default` themselves. The biggest issue with that currently is that PSRL doesn't notice the...

The interactive WG discussed this today and determined that it's likely due to a difference in how the runtime parameter binder works vs the psuedo parameter binder used by tab...

The Engine WG discussed this yesterday and agree to go forward with my proposal laid out in [`#9997 (comment)`](https://github.com/PowerShell/PowerShell/issues/9997#issuecomment-580743572) with the requirement that #18914 is implemented and the currently pubternal...

I was under the impression we were already caching the AST. I thought we stored them as `ScriptFile`'s and then just searched the AST with an `AstVisitor` each edit. If...

I'm going to fully flesh out what I mean here as it can be kind of confusing to visualize. Lets say you have three files. ## Script A ```powershell Get-ChildItem...

> > . All that said, I don't think it should ever wait for completion. > > I think that's been the behavior for a while now Yeah I was...