Michael Klement

I agree that an opportunity was missed, but please see the discussion in [Is it time for "PowerShell vZeroTechnicalDebt" and/or for an opt-in mechanism into new/fixed features that break backward...

@Kriegel: Glad to hear you found the OP useful, and thanks for your input. Just a few quick responses : > inside directly after the `Try {` put the `Statement...

@Kriegel > I am aware of most of your facts inside your response. I see. That wasn't obvious to me, since in your original comment you hadn't indicated awareness of...

Precisely: This is not an either-or situation: if we cant' fit everything into a single about_* topic, we can link to other, more detailed topics. But it is of prime...

> a page on the structure of a type.ps1XML [about_Types.ps1xml](https://github.com/MicrosoftDocs/PowerShell-Docs/blob/staging/reference/7.1/Microsoft.PowerShell.Core/About/about_Types.ps1xml.md) covers this, though I haven't looked at how comprehensively it does it. Some of what is in there currently could...

That's good to know, @sdwheeler, but that article is both very technical and abstract. It is focused on PSObject, which is mostly hidden (abstracted away) from PowerShell users and script...

Also, your article appears underneath the "Legacy PowerShell SDK" node in the documentation hierarchy, and none of the regular help topics seem to link to it (neither about_Types.ps1xml nor Update-TypeData,...

The problem is that https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_scopes#the-using-scope-modifier confuses _variables_ with their _values_. > This means it is possible to modify call scope variables in a different thread. A `$using:` reference only ever...

That is very strange - I see it too on my M1 Macbook Pro, although it takes about 1 minute. I'll have to investigate.

I'll look into it. It would have to be done via ANSI escape sequences.