DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=kiCQiLqSG/wWWuou
	P/H/9sJ6nGsgCric6peH56GGB9iJrUSrthjd5r7Wcc4od/+iNQT54JcA1DwEGCmU
	eI4my1ouA3RJqptFaN6QOTvGXG3yIhm3fwWdU9pD48pV53yO+EqBs+ndcdc5NTlE
	tct2kgGk3AF+/uubpRpsAxfELyA=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 26 Aug 2016 15:32:22 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <1647564591.20160826153222@yandex.ru>
To: Mark Hansen <cygwin@mehconsulting.com>, cygwin@cygwin.com
Subject: Re: The Cygwin User Guide on path names
In-Reply-To: <41bbca20-2b04-abba-4329-aefa7600cd13@mehconsulting.com>
References: <6a728c0c-81e8-b92b-8344-476d736e2306@cornell.edu>   <803530117.20160824125116@yandex.ru> <57BF15C7.40104@tlinx.org>  <1438370398.20160826055312@yandex.ru>  <41bbca20-2b04-abba-4329-aefa7600cd13@mehconsulting.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, Mark Hansen!

> On 8/25/2016 7:53 PM, Andrey Repin wrote:
>> Greetings, Linda Walsh!
>>
>>> Andrey Repin wrote:
>>>> Greetings, Ken Brown!
>>>>
>>>>> The documentation also says, "The usage of Win32 paths, though possible,
>>>>> is deprecated...."  I wonder if this should be strengthened to say
>>>>> something like, "The usage of Win32 paths, though possible, is strongly
>>>>> deprecated and may be removed in a future release of Cygwin."
>>>>
>>>> That would be the day Cygwin die for me.
>>>> --
>>>> With best regards, Andrey Repin
>>>> Wednesday, August 24, 2016 12:50:55
>>>> Sorry for my terrible english...
>>> ---
>>
>>> Curious -- but why?  How do you make use of win32 pathnames
>>> ( "C:\bin" versus "/bin" or "/c/bin" or "/cygdrive/c/bin" )
>>> depending on how your cygwin is configured).
>>
>> I make use of win32 paths directly.
>> diff and grep are the most used tools.
>>
>>> I'm wondering if maybe there is a misunderstanding?
>>
>> I don't think so.
>>
>>> For the most part -- many cygwin apps may not work
>>> correctly if given a win32 path in the same place you'd
>>> put a *nix path due to the backslashes being turned into
>>> quote sequences.
>>
>> That's too bad for such poor apps.
>>
>>> I mean, you can't type:
>>
>>>> ls C:\bin
>>>   (instead of )
>>>> ls /c/bin

> Can we differrentiate between C:/bin and C:\bin?

> I've always used C:/bin. Using drive identifiers and UNIX-style path separators.

> Is the proposal that this no longer be valid under cygwin?

There's (hopefully) no such proposal. Only a warning that it may not work in
all cases.


Also, @ Linda, the string escaping is done by the shell before passing
arguments to the command, as I understand.
If I'm starting an application not from shell, the app, being a good citizen,
should not second-guess the arguments it is given.


-- 
With best regards,
Andrey Repin
Friday, August 26, 2016 15:29:53

Sorry for my terrible english...


--
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