On Fri, 09 Mar 2007 11:39:18 -0500
Chet Ramey <[EMAIL PROTECTED]> wrote:
> Kevin F. Quinn wrote:
> > On Mon, 5 Mar 2007 17:49:47 -0500
> > Chet Ramey <[EMAIL PROTECTED]> wrote:
> >
> >> Bash-Release: 3.2
> >> Patch-ID: bash32-010
> >
> > I'm still seeing a difference in behaviour:
>
> Yes. Tha
Kevin F. Quinn wrote:
> On Mon, 5 Mar 2007 17:49:47 -0500
> Chet Ramey <[EMAIL PROTECTED]> wrote:
>
>> Bash-Release: 3.2
>> Patch-ID: bash32-010
>
> I'm still seeing a difference in behaviour:
Yes. That's the difference between the undefined quoting semantics
in bash-3.1 and the defined semanti
Tim Waugh wrote:
> There still doesn't seem to be a way to write expressions that work in
> 3.2 and in 3.1. For example, below is an expression that works fine in
> 3.1. How do I re-write it so that it (a) continues to work with
> bash-3.1, and (b) also works with bash-3.2?
>
> { cat "$file" ;
On Mon, 5 Mar 2007 17:49:47 -0500
Chet Ramey <[EMAIL PROTECTED]> wrote:
> Bash-Release: 3.2
> Patch-ID: bash32-010
I'm still seeing a difference in behaviour:
$ cat ~/bash-test
v="Alphabet"
[[ ${v} =~ "Alphabet" ]] && echo match 1 || echo no match 1
[[ ${v} =~ 'Alphabet' ]] && echo match 2 || ec
On Mon, 2007-03-05 at 17:49 -0500, Chet Ramey wrote:
> The glibc implementation of regcomp/regexec does not allow backslashes to
> escape "ordinary" pattern characters when matching. Bash used backslashes
> to quote all characters when the pattern argument to the [[ special
> command's =~ operator
BASH PATCH REPORT
=
Bash-Release: 3.2
Patch-ID: bash32-010
Bug-Reported-by:Ryan Waldron <[EMAIL PROTECTED]>
Bug-Reference-ID: <[EMAIL PROTECTED]>
Bug-Reference-URL:
http://lists.gnu.org/archive/html/bug-
