On Wed, Sep 09, 2009 at 11:56:54AM -0400, Mark J. Reed wrote: >On Wed, Sep 9, 2009 at 11:27 AM, Ziser, Jesse wrote: >>>> $ cmd /c echo "\"abc\"" >>>> "\"abc\"" >>>> >>>> # Wahhh?! >>>> >>>> Anyone who knows the explanation would make me very grateful. I've tried >>>> this with other Windows apps too, and the same weirdness seems to occur. > >Larry Hall: >>>All of the above is consistent with bash shell quoting. > >No, it's really not. Those backslashes should be long gone by the >time cmd.exe gets its arguments, yet it echoes them. It seems that >the Cygwin version of bash stops short before doing some of the work >it normally does itself on other systems, assuming the executed >command will have its command line run through the preprocessor in the >Cygwin DLL.
Actually, I'd say that was cmd doing something funky. It's hard to believe that bash was actually special-casing cmd.exe. cgf -- 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