Michael Klement

That's a much simpler workaround, @SeeminglyScience, thanks. In the absence of a dedicated event such as ` $ExecutionContext.InvokeCommand.PreExecutionAction` that should work fine (assuming `PSReadLine` is loaded, which is a reasonable...

See also: #15271, which also contains a more complete change-the-window-title-while-a-command-is-running workaround.

Ditto for me on the same macOS as yours, @sjsivert (15.0.1); the only obvious difference that my machine has an M1 Pro chip, but I wouldn't expect that to make...

Building on @rhubarb-geek-nz's comments: * Syntactically erasing the distinction between instance and static methods is ill-advised, as amply discussed; I'd be highly surprised if this were to ever be considered...

There is one cmdlet I can think of, and it does it _implicitly_: If the first input object (string) received by `ConvertFrom-Json` is not valid JSON by itself, it is...

Thanks for the suggestion, @stag-enterprises. Unfortunately, I'm not planning on adding new features to `perli`, but contributions are welcome.

While I haven't dug deep, there is definitely _something_ going on with respect to escape sequences, and it affects _all_ platforms: ```powershell [pscustomobject] @{ test = "`e[32mgreen`e[m" } | ft...

@rkeithhill: The `0` is optional; try the following (on any supported platform): ```powershell "before `e[32mgreen`e[m after" ```

Good point about the distinction between color codes and OSC sequences, @felixfbecker, and I think your guess about PowerShell not recognizing the latter is correct: ```powershell [pscustomobject] @{ test =...

Indeed; just to recap the simpler demonstration from above: ```powershell [pscustomobject] @{ test = "`e[32mgreen`e[m" } | ft -property @{ e='test'; width = 5 } ``` The fact that this...