2015-03-07 18:01:18 -0600, Eduardo A. Bustamante López:
> > But I am wondering if there is a walkaround to deal with errors in
> > <(). The ideal behavior should be that if there is a error in <(),
> > then we should not consider commandA is executed correctly even if its
> > return status is 0.
>
2015-03-07 16:46:52 -0600, Alan Wild:
> I'm really curious to see if anyone else offers better ideas, but the ways
> I've done this are
>
> 1) exactly what you propose.
>
> 2) use a subshell (parantheses):
>
> $ ( for x in a b c; { echo $x; } )
> a
> b
> c
> $ typeset -p x
> bash: typeset: x: no
It's not a bug, and the filename should be `bash'. `bash.info' is
created from bashref.info by doc/Makefile, and installed by `make
install'
I see. So my problem was that I downloaded bashref.info from the bash
web site and installed it manually into the directory that contains the
.
On 3/8/15 4:51 PM, Luc Teirlinck wrote:
> It's not a bug, and the filename should be `bash'. `bash.info' is
> created from bashref.info by doc/Makefile, and installed by `make
> install'
>
> I see. So my problem was that I downloaded bashref.info from the bash
> web site and installe
On 3/6/15 4:54 PM, Joseph Graham wrote:
> Hi,
>
> I don't know what the etiquette is for using this mailing list but I hope
> it's OK to just get straight to the bug.
>
> *STEPS TO REPRODUCE*
> 1. run the following commands to get everything set up:
>$ touch hiya
>$ mkdir '$HOME'
>$
On 3/7/15 11:20 PM, Luc Teirlinck wrote:
> I downloaded bashref.texi from your site. I believe that the following
> is a documentation bug:
>
> @direntry
> * Bash: (bash). The GNU Bourne-Again SHell.
> @end direntry
>
> After adding that line to the dir file and doing "C-h i"
Your code is horrible. Why do you have to alias stuff like declare -p?
Anyways.
> #!/bin/bash
> echo "Using:"
> bash --version|head -1
> shopt -s expand_aliases
> RA='declare -a'
> alias rs="IFS=\ $'\x09'$'\x0a'"
The fuck? Just use
alias rs="IFS=\$' \t\n'" or even better, alias rs='unset IFS'
Attached script shows a few examples
eventually it is split if the receiving var is already
an array, but you need to have saved and restore
IFS...
questions (at end of script)
why didn't statement pre-assignment work with
'echo' or 'let'?, but splitting assignment and
'echo' does work??
why d
I downloaded bashref.texi from your site. I believe that the following
is a documentation bug:
@direntry
* Bash: (bash). The GNU Bourne-Again SHell.
@end direntry
After adding that line to the dir file and doing "C-h i" in emacs, that
line did _appear_, but doing RETURN on it
