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=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
From: Mark Hansen <cygwin@mehconsulting.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@cornell.edu> <803530117.20160824125116@yandex.ru> <57BF15C7.40104@tlinx.org> <1438370398.20160826055312@yandex.ru> <41bbca20-2b04-abba-4329-aefa7600cd13@mehconsulting.com> <1647564591.20160826153222@yandex.ru> <57C34240.7080100@tlinx.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
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>

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