Michael Klement

@bitcrazed > Yes, I am very familiar with shells and shell syntax. Then you are undoubtedly familiar with the need to escape or quote the calling shell's metacharacters if you...

@TSlivede's point was that you currently cannot pass the meant-for-`bash` command line _as a single argument_ to `wsl.exe`, which would make the most sense. Aside from that, `wsl.exe` does _not_...

> This is by design. By _limiting_ design, because not only would passing the command line as a single string ease the escaping woes that prompted this issue, it would...

> `wsl.exe -- -u` does not work because the spell `bash -c '-u'` is invalid according to bash itself. Good point, I've also corrected the comment above. The reason is...

@mcuee, that is one of several _bugs_ in the parameter binder, and as such a separate issue (the workaround here is to pass `'-B0.5'`); see the following issues: * https://github.com/PowerShell/PowerShell/issues/6291...

You can get the (hopefully) full story and **workarounds** in [this SO answer](https://stackoverflow.com/a/48372333/45375) of mine, but the short of it is: As @markekraus has already stated, the PowerShell pipeline invariably...

@ThePieMonster: If you agree with my analysis, can you please change the title of this issue to something like "Piping text to an external program appends a trailing newline"?

@ThePieMonster: Thanks for updating the title. Unfortunately, `echo -n` does _not_ work with `cmd`, because `echo` is an _internal_ command that supports _no_ options at all, so the `-n` is...

@wclear: This issue is about the inability to send a string as-is TO an external program, without having PowerShell append a trailing newline. In the opposite direction, FROM an external...

@SteveL-MSFT: True, on the output side, due to parsing output into an _array_ of lines, PowerShell _also_ does _not_ allow you to distinguish between: ```powershell # On Unix: NO trailing...