Re: bash 4.1 command substitution

2010-08-09 Thread John Kelly
On Fri, 06 Aug 2010 17:31:08 +, John Kelly wrote: >>bash --version >>GNU bash, version 4.1.7(1)-release (i586-pc-interix3.5) >Backquote command substitution works, but $(...) does not. >I built it like this: >>CFLAGS="-O2 -march=i686" \ >>./c

bash 4.1 command substitution

2010-08-06 Thread John Kelly
>bash --version >GNU bash, version 4.1.7(1)-release (i586-pc-interix3.5) #! /usr/local/bin/bash one=`cat data` echo one=$one two=$(cat data) echo two=$two >one=abc >./xs: command substitution: line 7: syntax error near unexpected token `)' >./xs: command substitution: line 7: `cat data)' >two

Re: pipefail bug

2006-12-04 Thread John Kelly
On Mon, 04 Dec 2006 11:53:03 -0500, Chet Ramey <[EMAIL PROTECTED]> wrote: >> # With -e -o pipefail, this script should exit immediately upon returning >> # from the pipeline, since grep does not match its string, and returns 1. >This is not true, strictly speaking. The `-e' option applies to onl

pipefail bug

2006-12-02 Thread John Kelly
#!/bin/bash # With -e -o pipefail, this script should exit immediately upon returning # from the pipeline, since grep does not match its string, and returns 1. # However, any trivial compound statement at the end of the pipeline will # cause the script to continue running. It's possible to work