From: "Mark J. Reed" <markjreed@gmail.com>
To: cygwin@cygwin.com
Subject: Re: syntax for Cygwin bash invoking Win apps
Date: Wed, 09 Sep 2009 18:41:00 -0000 [thread overview]
Message-ID: <f60fe000909091141g54b9fa16v8d222b9f78771389@mail.gmail.com> (raw)
In-Reply-To: <622599.51453.qm@web30201.mail.mud.yahoo.com>
On Wed, Sep 9, 2009 at 2:20 PM, Ziser, Jesse wrote:
> --- On Wed, 9/9/09, Christopher Faylor [...] wrote:
>From: [...]
Please don't quote email addresses and message headers.
> OK, yeah, I now see that is basically what's going on.
> Bash is processing it as normal and then Cygwin is adding all kinds of quoting
> before invoking the Windows executable.
Makes sense. Bash is stripping the backslashes, but then Cygwin is
putting them back. So their apparent invulnerability is an illusion.
> However, it does more than quote them (which would only bother me a little),
> because it also added backslashes in front of the quote-marks
That is "quoting". In this context, "quoting" means "marking special
characters so that they are not interpreted according to their special
meaning", a.k.a. "escaping", and is not limited to quotation marks.
--
Mark J. Reed <markjreed@gmail.com>
--
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:[~2009-09-09 18:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 15:27 Ziser, Jesse
2009-09-09 15:57 ` Mark J. Reed
2009-09-09 16:05 ` Christopher Faylor
2009-09-09 16:10 ` Mark J. Reed
2009-09-09 16:31 ` Ziser, Jesse
2009-09-09 17:45 ` Christopher Faylor
2009-09-09 18:21 ` Ziser, Jesse
2009-09-09 18:41 ` Mark J. Reed [this message]
2009-09-09 16:10 ` Larry Hall (Cygwin)
-- strict thread matches above, loose matches on Subject: below --
2009-09-09 15:57 Ziser, Jesse
2009-09-22 19:28 ` Ziser, Jesse
2009-09-09 3:30 Ziser, Jesse
2009-09-09 4:31 ` Matt Wozniski
2009-09-09 4:40 ` Larry Hall (Cygwin)
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=f60fe000909091141g54b9fa16v8d222b9f78771389@mail.gmail.com \
--to=markjreed@gmail.com \
--cc=cygwin@cygwin.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).