And this is how. Quoting any part of the rhs forces it to be matched
as a string.
Okay, that's very clear. Maybe the man page could be updated?
Patch 39, which you appear to have applied, introduces a `compat31' shell
option which you may enable to restore the bash-3.1 behavior.
Ah! And
Alexis Huxley wrote:
Bash Version: 3.2
Patch Level: 39
Release Status: release
Description:
[[ ... =~ ... ]] is broken when RHS is quoted
The behavior changed, intentionally, between bash-3.1 and bash-3.2.
# As described by OP, =~ has stopped working:
lasagne$ bash
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale'
On Sun, Jun 22, 2008 at 12:07 PM, Alexis Huxley [EMAIL PROTECTED] wrote:
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu'
Description:
[[ ... =~ ... ]] is broken when RHS is quoted
from http://tiswww.case.edu/php/chet/bash/CHANGES :
f. Quoting the string argument to the [[ command's =~ operator now forces
string matching, as with the other pattern-matching operators.
Hmmm ... ok, thanks, I
On Sun, Jun 22, 2008 at 8:15 PM, Alexis Huxley [EMAIL PROTECTED] wrote:
Description:
[[ ... =~ ... ]] is broken when RHS is quoted
from http://tiswww.case.edu/php/chet/bash/CHANGES :
f. Quoting the string argument to the [[ command's =~ operator now forces
string matching, as
6 matches
Mail list logo
