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=SfTrOE3zjhFUDIkUrzC60ez1T63Dsx
	H2F6NCVEaDZH3cWGAgxOs+OGqWvwCG3Ph5W6RT5FV24rQmzDlijS/49Jgr6faFWA
	b698Jxd2ApQKQJER1yjHhp9K0DjgRsrdLoA3eXYmSF4uIqD/KZEaJB8xdU2WYyrb
	xWGls4stmgk6Q=
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=byBxlkC4GC+ndoU7emxhtgrdVKY=; b=HT2b
	Nef0AiVP7LQspsH5NnnrE7Y3MrD+wYysuapewLBMGn54GRqzaYuDFVyT1VWvnhz9
	fhatp5H/m/eLM2p5fAdiK1mLRvckMU4s331CtFEHTM8bsMSCENl7r+A9C5OT+C4T
	gHJv+tYQtP69tsJsmgLFUy2rPcPJ0FB6r+ltBDo=
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, citizen, linda
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:	Sun, 28 Aug 2016 13:30:13 -0700
Lines:	28
Message-ID:	<7b349b2a-25c2-94be-40fa-211cb6ad3cdd@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> <41bbca20-2b04-abba-4329-aefa7600cd13 AT mehconsulting DOT com> <1647564591 DOT 20160826153222 AT yandex DOT ru> <57C34240 DOT 7080100 AT tlinx DOT org>
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:	<57C34240.7080100@tlinx.org>
X-IsSubscribed:	yes

On 8/28/2016 12:57 PM, Linda Walsh wrote:
> Andrey Repin wrote:
>> 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.
> ---
> 	Absolutely.  Don't get me wrong.  I am NOT for removing
> functionality or compatibility.  If the Winpaths work for you
> in your situation, I am all for keeping them working!  No reason
> to break previous compatibility needlessly.  Way too often, developers
> are throwing away previous compat. because its convenient, to make
> it harder for the user to maintain & control their machine.
>
> 	I usually find the forward slashes easier to use because
> of the quoting issue -- as I used ls for an example.  Same would
> apply to diff though.  I.e. -- in bash, if you type
>
>   > diff C:\tmp\file1 C:\tmp\file2

But I wouldn't expect this to work, because I know the backslashes are going to
be interpreted by the shell. It's nothing to do with the application (diff in
this case). To use a command shell, you need to know what that shell does.

When using Cygwin, I use paths like C:/tmp/file1 or /cygdrive/c/tmp/file1.
Never C:\tmp\file1 (unless I'm quoting/escaping the backslashes as needed).




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