Re: Errors when patching bash4.0

2009-07-22 Thread Alex Reed
On Jul 22, 4:09 pm, Bob Proulx wrote: > Alex Reed wrote: > > At least one "hunk" fails on every patch file.  What am I doing wrong? > > Hmm...  Works for me.  Here is a trace of the important bits. > >   $ wgetftp://ftp.gnu.org/pub/gnu/bash/bash-4.0.tar.gz >   $

Errors when patching bash4.0

2009-07-22 Thread Alex Reed
Hello, I've downloaded and decompressed the bash-4.0 tarball, and downloaded bash40-001 through bash40-028 into a subdirectory bash-4.0/patches, using: bash $ tar xzvf bash-4.0.tar.gz bash $ cd bash-4.0 bash-4.0 $ mkdir patches bash-4.0 $ # line breaks added for clarity to you, the reader for i in

Re: mapfile usage

2009-02-04 Thread Alex Reed
On Feb 4, 2:59 pm, Stephane CHAZELAS wrote: > 2009-02-4, 10:50(-08), Alex Reed: > > > Can someone please explain how 'mapfile' should be used?  I am trying: > > > cat file.txt | mapfile > > for i in ${MAPFILE};do echo $i; done > > > and I see no

mapfile usage

2009-02-04 Thread Alex Reed
Can someone please explain how 'mapfile' should be used? I am trying: cat file.txt | mapfile for i in ${MAPFILE};do echo $i; done and I see no output. I've tried adding the -t option to strip trailing newlines. If I use the following command: mapfile -u file.txt I get the error: bash: mapfi

Re: globstar syntax

2009-01-22 Thread Alex Reed
Thanks Chet, and everyone who has contributed.

globstar syntax

2009-01-20 Thread Alex Reed
Should the globstar (**) syntax allow for partial parameter matching (i.e. **.c to find all *.c files in the current directory and its sub- directories)? Currently this can be implemented like this: for i in **; do if [[ ${i} =~ \.c$ ]]; then ; fi; done It would be pleasantly convenient if this w