DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:reply-to:to:subject:date:message-id
	:references:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=GrhKnosofE8EMxMut5/Rz/2uSVFlU
	hrYckdYcHmcnMXOJOWmB1qaWKN7xXanXmEfekkdTpKSEZyytNJQKFjTebApLw81V
	pe9XC+ornM73kXCeWc9zgzTAIFhQP2oxRIM/6ApiMhBmxZJt1TriIB9tmN3QNK5A
	mc/At48qKR5QhA=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Stephen Provine via cygwin" <cygwin@cygwin.com>
Reply-To: Stephen Provine <stephpr@microsoft.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>,
        "Brian.Inglis@SystematicSw.ab.ca"	<Brian.Inglis@SystematicSw.ab.ca>
Subject: RE: Command line processing in dcrt0.cc does not match Microsoft parsing rules
Date: Fri, 30 Aug 2019 20:59:12 +0000
Message-ID: <MWHPR21MB0845F78385792965A94E0CD9B9BD0@MWHPR21MB0845.namprd21.prod.outlook.com>
References: <MWHPR21MB08452919F35B1B0C5F0EB4DCB9BD0@MWHPR21MB0845.namprd21.prod.outlook.com>
In-Reply-To: <MWHPR21MB08452919F35B1B0C5F0EB4DCB9BD0@MWHPR21MB0845.namprd21.prod.outlook.com>
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-userprincipalname: cFpqeO2hF7eiEtyk7iCQ4whRqt23BN2MQGY+xo+JRtwcN+Z25B9olBC6yLTRAe8H9AjMMMITUn+tMm5Nxr5lHQ==
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id x7UKxpoq002536

> Cygwin command line parsing has to match Unix shell command line processing,
> like argument splitting, joining within single or double quotes or after a
> backslash escaped white space characters, globbing, and other actions normally
> performed by a shell, when any Cygwin program is invoked from any Windows
> program e.g. cmd, without those Windows limitations which exclude any use of a
> backslash escape character except preceding another or a double quote.

I guess my assumption was that the "winshell" parameter would be used to determine
when a Cygwin process is called from a non-Cygwin process and that it would be more
appropriate to use standard Windows command line processing (as limiting as it may
be) in that case. Once in the Cygwin environment, calls from one process to another
should obviously process command lines according to Unix shell rules.

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