Re: Bash-3.1.17 gets lost looking for end of string in certain contexts

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Richard on 5/1/2006 5:46 PM:
> 
> 602   status=`echo 'beriberi'| { ${GREP} -E -e '(....).*\1' >/dev/null 2>&1 ; 
> echo $?; }`

I could not reproduce this - are you sure you reported it correctly?

$ foo=`echo 'beriberi'| { grep -E -e '(....).*\1' >/dev/null 2>&1 ;
> echo $?; }`
$ echo $foo
0
$ echo `echo 'beriberi'| { grep -E -e '(....).*\1' >/dev/null 2>&1 ;
> echo $?; }`
0
$ echo $BASH_VERSION
3.1.17(6)-release

However, there are still some known issues with `` command substitution
parsing in bash-3.1 that have been previously reported, such as
http://lists.gnu.org/archive/html/bug-bash/2006-03/msg00039.html.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEV01v84KuGfSFAYARAmSWAJ9Rx4cdXJ4v19QtndJkV5JsKb6s0gCgt6c2
AxNqtFlldig+XZv4YqKGLCA=
=l1nt
-----END PGP SIGNATURE-----