Re: BASH bug or expected behaviour?

Dean K. Gibson wrote: > In GNU Bash-2.05b (Fedora Core 1), I observe the following behaviour: > > If bash script A is invoked (via "source") with command line parameters, > and bash script A invokes (via "source") bash script B with NO > parameters specified, then the parameters specified for A ar

Re: BASH bug or expected behaviour?

Dean K. Gibson wrote: > If bash script A is invoked (via "source") with command line parameters, > and bash script A invokes (via "source") bash script B with NO > parameters specified, then the parameters specified for A are passed to > B (rather than what I would have thought would be the expe

Bash completion buggy if -o nospace, -o filenames and -W used together.

Hello, I've found a bug in bash autocompletion... Configuration Information [Automatically generated, do not change]: Machine: i586 OS: linux Compiler: gcc -I/usr/src/packages/BUILD/bash-3.0 -L/usr/src/packages/BUILD/bash-3.0/../readline-5.0 Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE

BASH bug or expected behaviour?

In GNU Bash-2.05b (Fedora Core 1), I observe the following behaviour: If bash script A is invoked (via "source") with command line parameters, and bash script A invokes (via "source") bash script B with NO parameters specified, then the parameters specified for A are passed to B (rather than w