Michael Klement
Michael Klement
@JamesWTruher, with respect to _batch files_: > with a batch file, the `=` seems to be a token separator Specifically, unquoted ` , ; =` interchangeably act as argument separators...
The [initial post](https://github.com/PowerShell/PowerShell/issues/15143#issue-849198498) details the proposed accommodations and their benefits and [this follow-up comment](https://github.com/PowerShell/PowerShell/issues/15143#issuecomment-822805995) provides examples of what we would _gain_. Perhaps it is helpful to complement that with **examples...
Accommodation F is definitely the _least_ important accommodation, and the failure is unequivocally `cmd.exe`'s fault (details [here](https://github.com/PowerShell/PowerShell/issues/14747#issuecomment-800376364)). But I still think it's worth doing: * Because it's one less thing...
P.S., @TSlivede: Special-casing `cmd.exe` calls is unavoidable unless we want to _break_ the following (`cmd /c ""`, which I feel strongly we shouldn't), which: * currently works, but due to...
> I don't think, that's really necessary, I don't feel strongly about Accommodation F, given that not all `cmd.exe` command lines could be passed as individual arguments using PowerShell syntax....
> this is based on internal partner feedback using this experimental feature You're confirming @KirkMunro's [point](https://github.com/PowerShell/PowerShell/pull/10238#issuecomment-826091414). The sad thing about this decision is that in this case _there is no...
The saga continues at https://github.com/PowerShell/PowerShell/pull/15408#issuecomment-863458289
@KevinMarquette: While it's a good idea to take full advantage of the parameter "plumbing" in general, that is a separate issue from _building friendly user interfaces_, notably _for non-PS-savvy users_....
> PowerShell currently makes if VERY difficult PowerShell is a _shell_ - just like `cmd.exe` and `bash` are. This means: you need to understand and accommodate the running shell's syntax...
> are you aware of any other documentation (including 3rd party) that states otherwise? I don't think it's covered in the official documentation, but I've summarized the behavior and limitations...