On Fri, Aug 08, 2008 at 02:47:43PM -0500, Tim McDaniel wrote: > On Fri, 8 Aug 2008, Christopher Faylor > <[EMAIL PROTECTED]> wrote: >> On Fri, Aug 08, 2008 at 01:58:12PM -0500, Tim McDaniel wrote: >>> That's most unpleasant. I don't suppose there's any way to control >>> Cygwin's bash in re where to put double quotes around arguments >>> being passed to a Windows command (since getting Microsoft to make >>> explorer.exe be sane is hopeless)? Except by not using characters >>> that bash thinks need quoting. >> >> I'd be very surprised if bash was doing anything different for >> Windows than it does for linux. cygwin1.dll does do some quoting of >> arguments to non-cygwin programs if it thinks it is required. > > Well, *something* had to be adding the double-quotes. It's execve() > and such adding them, then?
I said cygwin1.dll. Isn't that all-encompassing enough? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
