> >echo-win32.exe C:\"Program Files"\ > echo-win32.exe > C:"Program > Files\ > > Is this as you expected? > > >echo.exe C:\"Program Files"\ > echo > C:\Program Files\ > > This makes more sense to me.
That is as expected. It is the way a Windows program would split the command line. To me, it does not make sense that Cygwin programs process the command line, which was produced by a Windows program, in a manner which is inconsistent with how a Windows program would. If the sole purpose of taking a Windows command line is being able to be called from a Windows program, how does it make sense to diverge from Windows' parsing logic, aside from handling at-files? It sadly breaks builds driven by Windows-native tools since they expect the standard command line handling. ________________________________ LÖWEN ENTERTAINMENT GmbH • Saarlandstraße 240 • 55411 Bingen am Rhein • Geschäftsführung: Christian Arras (Vorsitzender), Oliver Bagus, Dr. Daniel Henzgen • Vorsitz im Aufsichtsrat: Uwe Christiansen • Amtsgericht Mainz • HRB 23327 • USt.-IdNr. DE148266135 • WEEE-Reg.-Nr. DE 53361450 • Tel.: +49 6721 407 0 • E-Mail: [email protected] -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
