Michael Klement

Interesting, @SteveL-MSFT - can you point us to the source code? What it outputs with width 4 is ``"`e..."``, i.e., it blindly takes the first 4 chars., as previously stated...

Thanks for the source-code link, @SteveL-MSFT. > but we can avoid the complexity of calculating a closing sequence by always resetting the console between columns. That is certainly preferable to...

I do like the idea of leaving the escape sequences while being _content_-length-aware, @jazzdelightsme, because it gives us the best of both worlds: * proper truncation based on the count...

Thanks, @oising - indeed it works fine in VT, and at least on some Linux distros (I've tried Ubuntu 18.04), but _not on macOS_ (neither in Terminal.app nor in iTerm2.app),...

Indeed, inline splatting would be nice. This was first proposed a long time ago: * Rejected RFC: https://github.com/PowerShell/PowerShell-RFC/blob/master/Archive/Draft/RFC0002-Generalized-Splatting.md * Related discussion: https://github.com/PowerShell/PowerShell-RFC/issues/6 * A related PR that was therefore ultimately...

@237dmitry, your example is unrelated to [splatting](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_Splatting), which this issue is about. Please consider hiding or deleting your comment (in response to which I'll hide / delete mine).

Speaking in no official capacity whatsoever: My personal sense is that the RFC process is all but dead (as of this writing, there are no drafts except an accepted one...

Good point, @237dmitry; another potential problem source is telemetry, which can be deactivated by setting environment variable `POWERSHELL_TELEMETRY_OPTOUT` to `1`

I'll leave the review to others, @ArmaanMcleod, but thank you for tackling this.

@JunielKatarn, please see https://github.com/PowerShell/PowerShell/issues/23906#issuecomment-2358953602