m...@ice.filescope.com wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i686
> OS: linux-gnu
> Compiler: i686-pc-linux-gnu-gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
> -D
The -c option for declare (new in bash 4.0) is not mentioned in either
the man page or the "help declare" text.
Greg Wooledge wrote:
> The -c option for declare (new in bash 4.0) is not mentioned in either
> the man page or the "help declare" text.
Correct. I'm not sure the capitalization feature will survive. If it
makes it into the next version, I will add the documentation.
--
``The lyf so short, the
You know those pesky error messages,
nurdsome: line 17: warning: here-document at line 1 delimited by end-of-file
(wanted `EOF')
Well there should be a new 'trick': <<$EOF, <<\$EOF, or something, the
meaning of which is 'I really mean to go all the way to the end of the
file'.
This is in additio
I think I just found a bug in the version of bash that ships with
Ubuntu 8.04 and 8.10; I've tested and reproduced it across x86_64 and
i386/i586 distributions as well as the server/desktop distributions.
Anybody else seen this in the wild?
From: dgets...@mywork.net
To: bug-bash@gnu.org,b...@packa
Hello,
With bash-4.0-10 I get following behavior:
$ touch 'a file with spaces'
$ touch 'a File with spaces'
$ touch 'a File With spaces'
$ cat a
After pressing TAB completion seems to stop working, pressing Ctrl-i (another
bind for `complete') also doesn't work, using Alt+/ (bind for complete-f
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash
