>
> Recently I found shell is a nice program that can be extended to solve my
> automatic regression test problem. So I started hacking it.
> I found it would be easiler use $(wildcard) in the builtins/Makefile.in, in
> stead of staticly specify all the source files:
Unfortunately, it is an ext
Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba
So, apparently, sometime between bash-2.05a and bash-3.0, a change was made
to the job control commands. It used to be the case that typing "%" on a
line by itself would foreground the most recent job, just as if you had
typed "fg" or "%+". In bash-3.0, this prints the error message:
bash: fg: %:
I found a redirection bug in bash 2.05b. I didn't see anything
similar searching gnu.bash.bug, so I think this is new.
Bash 2.05b fails with a bad file descriptor message when attempting
certain complicated redirections. In the example below I am trying
to tee stderr while also passing stderr t
