On 9/5/19 9:26 PM, Eric Blake wrote: > Rather, go is not passing the command line to CreateProcess in the way > that is unambiguously parseable in the manner expected by > CommandLineToArgvW.
The specific example I gave is unambiguous and is parsed correctly by CommandLineToArgvW, so if the goal is for Cygwin to effectively simulate this function, I can confirm that it is missing this case. It's reasonable that Go's algorithm should be changed to have a better chance of working with Windows programs that manually implement command line parsing and may not match expectations for all cases. I'll follow up with them and for the time being, work around the issue with my own implementation as I've since figured out how to do that. FWIW, here's the most definitive reference I've found for how Windows binaries compiled with the Microsoft C/C++ compilers do command line parsing, in case there is any desire to address this issue at some point: http://daviddeley.com/autohotkey/parameters/parameters.htm#WINCRULES Thanks for entertaining my persistence on this topic! Stephen -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple