X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <622599.51453.qm@web30201.mail.mud.yahoo.com> References: <20090909174534 DOT GD29151 AT ednor DOT casa DOT cgf DOT cx> <622599 DOT 51453 DOT qm AT web30201 DOT mail DOT mud DOT yahoo DOT com> Date: Wed, 9 Sep 2009 14:41:32 -0400 Message-ID: Subject: Re: syntax for Cygwin bash invoking Win apps From: "Mark J. Reed" To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT 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 -- 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