From: Andrey Repin <anrdaemon@yandex.ru>
To: Stephen Provine <stephpr@microsoft.com>, cygwin@cygwin.com
Subject: Re: Command line processing in dcrt0.cc does not match Microsoft parsing rules
Date: Sat, 07 Sep 2019 12:05:00 -0000 [thread overview]
Message-ID: <135817606.20190906233445@yandex.ru> (raw)
In-Reply-To: <MWHPR21MB0845282E7582DC95ADF0F140B9BB0@MWHPR21MB0845.namprd21.prod.outlook.com>
Greetings, Stephen Provine!
> On 2019-09-04 23:29, Brian Inglis wrote:
>> As standard on Unix systems, just add another level of quoting for each level of
>> interpretation, as bash will process that command line, then bash will process
>> the script command line.
> My mistake - I'm very aware of the quoting rules, yet in my test script for this
> scenario I forgot to quote the arguments. However, if POSIX rules are being
> implemented, there is still something I didn't expect. Here's my bash script:
> #!/bin/bash
> echo "$1"
> echo "$2"
> echo "$3"
> And I invoke it like this from a Windows command prompt:
> C:\> bash -x script.sh foo bar\"baz bat
> + echo foo
> foo
> + echo 'bar\baz bat'
> bar\baz bat
> + echo ''
> Not expected. Called from within Cygwin, the behavior is correct:
Again, fully expected.
> $ bash -x script.sh foo bar\"baz bat
> + echo foo
> foo
> + echo 'bar"baz'
> bar"baz
> + echo bat
> bat
> Can you explain this difference?
CMD escape character is ^, not \
> The reason I ask is that if this worked,
> the way Go constructs the command line string would be just fine.
No.
--
With best regards,
Andrey Repin
Friday, September 6, 2019 23:33:46
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
WARNING: multiple messages have this Message-ID
From: Andrey Repin <anrdaemon@yandex.ru>
To: Stephen Provine <stephpr@microsoft.com>, cygwin@cygwin.com
Subject: Re: Command line processing in dcrt0.cc does not match Microsoft parsing rules
Date: Sat, 07 Sep 2019 12:20:00 -0000 [thread overview]
Message-ID: <135817606.20190906233445@yandex.ru> (raw)
Message-ID: <20190907122000.skla7GbBkxEr95QfQKCb-U-wKXslm1c2jQX7uGxnPMQ@z> (raw)
In-Reply-To: <MWHPR21MB0845282E7582DC95ADF0F140B9BB0@MWHPR21MB0845.namprd21.prod.outlook.com>
Greetings, Stephen Provine!
> On 2019-09-04 23:29, Brian Inglis wrote:
>> As standard on Unix systems, just add another level of quoting for each level of
>> interpretation, as bash will process that command line, then bash will process
>> the script command line.
> My mistake - I'm very aware of the quoting rules, yet in my test script for this
> scenario I forgot to quote the arguments. However, if POSIX rules are being
> implemented, there is still something I didn't expect. Here's my bash script:
> #!/bin/bash
> echo "$1"
> echo "$2"
> echo "$3"
> And I invoke it like this from a Windows command prompt:
> C:\> bash -x script.sh foo bar\"baz bat
> + echo foo
> foo
> + echo 'bar\baz bat'
> bar\baz bat
> + echo ''
> Not expected. Called from within Cygwin, the behavior is correct:
Again, fully expected.
> $ bash -x script.sh foo bar\"baz bat
> + echo foo
> foo
> + echo 'bar"baz'
> bar"baz
> + echo bat
> bat
> Can you explain this difference?
CMD escape character is ^, not \
> The reason I ask is that if this worked,
> the way Go constructs the command line string would be just fine.
No.
--
With best regards,
Andrey Repin
Friday, September 6, 2019 23:33:46
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
next prev parent reply other threads:[~2019-09-07 12:05 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
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 [this message]
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=135817606.20190906233445@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--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).