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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=ruW7F1fBFZI2VS1N4fDzCRnvnFd+HcLCBngzWJjJnn2
	j1LRGCYiYxt/GxUWK0NBzbRqBflsz6ZBtSR/raOboQwRRrM8Mwbbonukci9GrD2O
	AoDcMtO0mPbrZpbyz4w7cTpXOq6w/6LzAsPTF7Qj+DUt8mPsIdZUdU5PzjOPI48Y
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=9NXj+gC64RZEHlEhZUyEjM3Y7IA=; b=o53aMABAl8G8/bAva
	ZWcJzCvIye/oe1j/dq9Rp+u1Q6OC0OZwZ/09nN0jW56cUGS2RVCEz5NbeVPWthmC
	T6M9KE9yAe/jl3GTxsTDV6PNf3RxyrW4Nn1tBKuxDIJsstSpn8fYT5q8ZGg4fKjU
	U5XyUaISJJSPZaeKrp0iSYcHio=
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.6 required=5.0 tests=BAYES_50,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=rings, versus, H*r:192.168.3, H*r:8.14.7
X-HELO: Ishtar.sc.tlinx.org
Message-ID: <57BF15C7.40104@tlinx.org>
Date: Thu, 25 Aug 2016 08:59:03 -0700
From: Linda Walsh <cygwin AT tlinx DOT org>
User-Agent: Thunderbird
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: The Cygwin User Guide on path names
References: <6a728c0c-81e8-b92b-8344-476d736e2306 AT cornell DOT edu> <803530117 DOT 20160824125116 AT yandex DOT ru>
In-Reply-To: <803530117.20160824125116@yandex.ru>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

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'm wondering if maybe there is a misunderstanding?

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.  I mean, you can't type:

> ls C:\bin 
  (instead of )
> ls /c/bin

and have it work, since the first would
turn into: "ls C:bin" (or if the \b is taken
as an escape sequence, it rings the bell, so it
could be translated as "ls C:\008in".  So I'm wondering
where you know the backslash form would always work and
wouldn't be mangled "somewhere"...?  (If you see what
I mean?)

*cheers*
-linda



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