Michael Klement

I don't see this behavior either. @MovGP0: Please try to provide a minimal verifiable example.

Good idea, @kilasuit, but `-Wait` needs to be added to your `Start-Process` command (otherwise the calling shell and the newly launched one will compete for interactive input).

Good idea, but I suggest calling the parameter `-Stream` instead, analogous to `Out-String`'s conceptually related parameter. It's also worth spelling out how this will affect the output for multiple input...

Thanks, @paulhilchey, but note that `-Compress` is incidental to the issue at hand; I merely used it to show the current output for multi-object input more concisely.

I also cannot reproduce the problem, at least with the `PSWriteColor` module. The `-Version` parameter is explicitly documented as being version-exact (no need for `[...]` enclosure), and that to get...

On second thought: * The [Package Versioning](https://learn.microsoft.com/en-us/nuget/concepts/package-versioning?tabs=semver20sort#version-ranges) rules seem to be based on _semver_ version numbers, which are limited to _three_ components, with an optional suffix. * Therefore, `2024.5.20.1` is...

I cannot speak to the design intent, but I can explain the logic governing the de facto behavior (which never changed, as far as I know): * If `Get-ChildItem` matches...

Definitely a bug - it seems that (the implementing class behind) `Clear-Content` is called behind the scenes, which triggers the extra prompt. Not only should the `Clear-Content` prompt not show,...

I agree that not failing and outputting `$false` is the more sensible behavior, given that the very purpose of the cmdlet is to test the validity of the given path...

I do empathize in general - though I observe no difference in error handling between a profile and a regular script. As noted, I suspect this proposal won't go anywhere...