MIME-Version: 1.0
In-Reply-To: <622599.51453.qm@web30201.mail.mud.yahoo.com>
References: <20090909174534.GD29151@ednor.casa.cgf.cx> 	 <622599.51453.qm@web30201.mail.mud.yahoo.com>
Date: Wed, 9 Sep 2009 14:41:32 -0400
Message-ID: <f60fe000909091141g54b9fa16v8d222b9f78771389@mail.gmail.com>
Subject: Re: syntax for Cygwin bash invoking Win apps
From: "Mark J. Reed" <markjreed@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.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.
> =C2=A0Bash 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 littl=
e),
> 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.

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