Bizarre Cygwin/Explorer/paths problem half-solved

Fri Aug 8 19:48:00 GMT 2008

On Fri, Aug 08, 2008 at 01:39:49PM -0400, Lev Bishop wrote:
>On Fri, Aug 8, 2008 at 12:28, Christopher Faylor wrote:
>>>> Is there any documentation on who rewrites arguments, under what
>>> conditions, and how they're altered?
>>>> I missed this when it was first mentioned. Cygwin doesn't munge command
>> line arguments. Why would it assume that /e,something was a windows
>> path? That makes no sense.
>>Nobody is munging anything.
>>What's going on here is as simple as the difference:
>>bash-3.2$ cmd /c echo "a b c"
>"a b c"
>bash-3.2$ cmd /c echo a b c
>a b c
>>There's really no more to it than that.

Yes. I understand. There was one message which indicated that cygwin
was converting paths on the command line which is, of course, nonsense.
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/