Greg Schafer wrote:
It appears there might be problem with this patch. Here is a test case I
distilled from the grep-2.5.1a testsuite:
status=`echo '-'| { ${GREP} -E -e 'a\' /dev/null 21 ; echo $?; }`
Put that line into a file called myfile then run like this:
# bash -n myfile
Greg Schafer wrote:
It appears there might be problem with this patch. Here is a test case I
distilled from the grep-2.5.1a testsuite:
status=`echo '-'| { ${GREP} -E -e 'a\' /dev/null 21 ; echo $?; }`
Put that line into a file called myfile then run like this:
# bash -n myfile
BASH PATCH REPORT
=
Bash-Release: 3.1
Patch-ID: bash31-010
Bug-Reported-by: [EMAIL PROTECTED]
Bug-Reference-ID: [EMAIL PROTECTED]
Bug-Reference-URL:
http://lists.gnu.org/archive/html/bug-bash/2006-01/msg00090.html
sorry if this comes thru' twice
Chet Ramey wrote:
There is a difference in behavior between bash-3.0 and bash-3.1 involving
parsing of single- and double-quoted strings occurring in old-style
command substitution. The difference has to do with how backslashes are
processed. This patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Greg Schafer on 2/21/2006 8:20 PM:
status=`echo '-'| { ${GREP} -E -e 'a\' /dev/null 21 ; echo $?; }`
Even shorter - from the command line:
bash-3.1.9 $ echo `echo 'a\'`
a\
bash-3.1.10 $ echo `echo 'a\'`
# Oops, bash is still
