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=eyHPI4ONVJZgzUjO
	v/dMB1wG/al/SecW+QdVAKusFlNbLEFpuex46pJHtY1xiAf6GS1x1txba+ACuY0U
	PFSxunghxR/9fHpj9++GEq5i2uMIysXpEcfnABjq94Gw8mLEiFtUsKrqWKL5Gx1f
	ZFBzHRzevLKMPhwKSfOr1NsiFtQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Mon, 29 Aug 2016 16:57:18 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <151740036.20160829165718@yandex.ru>
To: Linda Walsh <cygwin@tlinx.org>, cygwin@cygwin.com
Subject: Re: The Cygwin User Guide on path names
In-Reply-To: <57C34240.7080100@tlinx.org>
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=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, Linda Walsh!

> 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

> It won't do what many might think it 'should', -- it will
> try to compare "C:tmpfile1" & C:tmpfile2, with the backquotes
> removed before diff or patch ever see the filenames.  

Yes, that's expected because of the shell you're using.
But if you're, say, in a file manager, and want to compare two files (or
directories) on the opposite panels...

Alt+Shift+D =>
view:<? diff -x "CVS" -x ".svn" -I "\$Id.*\$" -I "\$Rev.*\$" -I "\$Date.*\$" -I "\$Author.*\$" -I "\$URL.*\$" -I "^Orbiting .*$" !?$UnixDiff$Options ((-c, -b etc.)):?! --strip-trailing-cr -- "!#!\!.!" "!^!\!.!"
 => the results are in the internal viewer and you can conveniently browse
through them and cross-reference the files as needed.


-- 
With best regards,
Andrey Repin
Monday, August 29, 2016 16:52:03

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