From: "Stephen Provine via cygwin" <cygwin@cygwin.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 21:21:00 -0000 [thread overview]
Message-ID: <MWHPR21MB0845F78385792965A94E0CD9B9BD0@MWHPR21MB0845.namprd21.prod.outlook.com> (raw)
In-Reply-To: <MWHPR21MB08452919F35B1B0C5F0EB4DCB9BD0@MWHPR21MB0845.namprd21.prod.outlook.com>
> 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
next prev parent reply other threads:[~2019-08-30 20:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 19:31 Stephen Provine via cygwin
2019-08-30 20:53 ` Brian Inglis
2019-08-30 21:21 ` Stephen Provine via cygwin [this message]
2019-08-31 4:18 ` Brian Inglis
2019-09-03 16:38 ` Stephen Provine via cygwin
2019-09-04 16:20 ` Brian Inglis
2019-09-04 23:46 ` Stephen Provine via cygwin
2019-09-05 5:29 ` Brian Inglis
2019-09-05 18:31 ` Stephen Provine via cygwin
2019-09-05 19:05 ` Eric Blake
2019-09-05 22:01 ` Stephen Provine via cygwin
2019-09-05 22:46 ` Eric Blake
2019-09-05 23:45 ` Stephen Provine via cygwin
2019-09-06 0:46 ` Steven Penny
2019-09-06 1:26 ` Eric Blake
2019-09-06 6:20 ` Stephen Provine via cygwin
2019-09-07 21:50 ` Brian Inglis
2019-09-07 12:05 ` Andrey Repin
2019-09-07 12:20 ` Andrey Repin
2019-09-09 16:47 ` Stephen Provine via cygwin
2019-09-09 16:57 ` Stephen Provine via cygwin
2019-09-09 17:11 ` Eric Blake
2019-09-09 19:05 ` Duncan Roe
2019-09-09 19:44 ` Andrey Repin
2019-09-10 12:43 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MWHPR21MB0845F78385792965A94E0CD9B9BD0@MWHPR21MB0845.namprd21.prod.outlook.com \
--to=cygwin@cygwin.com \
--cc=Brian.Inglis@SystematicSw.ab.ca \
--cc=stephpr@microsoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).