DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=rxivMAlg6tNXniXbHmt5PjhnOa/8N
	jW8DDxTjkVQlX5HA03z1FaUhIvYpTIVGZ4Bxlg6oKkbHvVkDxR7C8W4ZTrX6t4IX
	hXQpBfEI5gWPl9/dWgmlfn6GGD/Dvnj/S/+hXUgLRRZzLgBwzkbZ1lXQaEQw3Cja
	hTG4GWj2K+6Aho=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
From: Mingye Wang <arthur200126 AT gmail DOT com>
Date: Thu, 10 Oct 2019 16:30:13 +0800
Message-ID: <CAD66C+YN9n6t+z2RDJvOJshZoxgSWXsqvwpT1cyknoGEm0U3uQ@mail.gmail.com>
Subject: Re: [bug] globify dospath reacts poorly with escaped double quotes
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset="UTF-8"

On Tue, 8 Oct 2019 14:09:18 -0600, Brian Inglis wrote:

> Msys2 tools have to make their own arrangements if they support native Windows
> paths.
> Personally I found when I used to use DOS and Windows tools, it was easier using
> slashes instead of backslashes as directory separators, as most interfaces did
> not care, including most DOS & Windows APIs.

Use the source, Luke. Globbing on the cmdline, as we all know, is
something you only
care about when you are *not* passing in arguments from a Unix-type cmdline, and
build_argv in dcrt0.cc does *only* run globify if the parent process is *not*
Cygwin-powered.

> Backslash escaping and switching enclosing quotes on shell command lines...

See above.

--
Mingye Wang (Artoria2e5)

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