Subject: Re: Re: Why bash failed to match this pattern?
From: "Mark J. Reed" <[email-masked]>
To: Pan ruochen <[email-masked]>
Cc: [email-masked]
Date: Fri, 5 Jun 2009 02:47:28 -0400
List-Id: <cygwin.cygwin.com>

On Fri, Jun 5, 2009 at 2:35 AM, Pan ruochen
> But some bash does match the pattern:

It's possible that the behavior has changed between bash versions, but
the behavior is not Cygwin-specific.  3.2.17 on OS X also suppresses
metacharacters with quotation marks, and the documentation indicates
that this is the expected behavior. See

http://www.gnu.org/software/bash/manual/bashref.html#Conditional-Constructs

Under [[...]],  third paragraph: "An additional binary operator, ‘=~’,
is available [...] Any part of the pattern may be quoted to force it
to be matched as a string."

> $bash --version
> GNU bash, version 3.2.33(1)-release (i386-redhat-linux-gnu)
> Copyright (C) 2007 Free Software Foundation, Inc.
>
> Maybe some settings affect bash's behaviour.
>
> PRC
>

-- 
Mark J. Reed <[email-masked]>

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/