X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding
	:in-reply-to; q=dns; s=default; b=Yzt8SASnUpNfirpCR9MZJQ7dB794mD
	7ZWAKi7Fg32wJrHjX6M3aow3Us/i1EPvf6FTrf+Kku0Emnuauru2VKcM4/Ag3Adi
	bJdPSlKfqSfmlVoCSEo1bZp9RYJGXckYU5TFfnoEEJwzuJIe3ss5p9GJwN5p2fri
	HYhANyH7dBHXo=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding
	:in-reply-to; s=default; bh=4edGHzzihRTIcqXGDaM9d2J8Xug=; b=Qk+G
	nxTvAoJ5ljpmr6PrVJhYZNfAT/7/+1VSyjJeoKs/WaTyIGbkeFibmBx9rVJBYEtb
	/7dsyc9H0nprdFA424ImGv+flUT3eGH1wHIFHT0g1QIG0U9B7gPC3BTIJ0xIAq/p
	GzRrGksnxLay85pA1Qaz9ug3+J5CP5pd5vEoYDI=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=H*r:Unknown, linda, H*F:U*cygwin
X-HELO:	blaine.gmane.org
To:	cygwin AT cygwin DOT com
From:	Mark Hansen <cygwin AT mehconsulting DOT com>
Subject:	Re: The Cygwin User Guide on path names
Date:	Fri, 26 Aug 2016 05:09:11 -0700
Lines:	47
Message-ID:	<41bbca20-2b04-abba-4329-aefa7600cd13@mehconsulting.com>
References:	<6a728c0c-81e8-b92b-8344-476d736e2306 AT cornell DOT edu> <803530117 DOT 20160824125116 AT yandex DOT ru> <57BF15C7 DOT 40104 AT tlinx DOT org> <1438370398 DOT 20160826055312 AT yandex DOT ru>
Mime-Version:	1.0
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
In-Reply-To:	<1438370398.20160826055312@yandex.ru>
X-IsSubscribed:	yes

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?


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

- Raw text -