w8...@mail.petersen.net wrote:
> cd()
> {
>builtin cd "$0" && xtitle $HOST: $PWD
> }
>
> This no longer works correctly since I upgraded bash to the version
> listed above. Instead, when I use cd without an argument the following
> error message:
>
> -bash: $@: unbound variable
>
> Repeat-
Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: freebsd5.4
Compiler: cc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386'
-DCONF_OSTYPE='freebsd5.4' -DCONF_MACHTYPE='i386-portbld-freebsd5.4'
-DCONF_VENDOR='portbld' -DLOCALEDIR='/usr/local/share/loc
A small typo in the bash doc.
Andreas.
--- doc/bashref.texi.~1~2009-02-18 21:14:43.0 +0100
+++ doc/bashref.texi2009-03-14 21:11:36.0 +0100
@@ -864,7 +864,7 @@ operator terminates a pattern list.
A list of patterns and an associated command-list is known
as a @var{cla
Clark J. Wang wrote:
> With bash version: 4.0.10, the following case statement crashed with
> segfault:
>
> $ cat foo.sh
> case a in
> a) echo a ;&
> esac
> $ bash4 foo.sh
> a
> Segmentation fault
> $
>
> In an interactive shell, that case statement causes current shell to hang
> with nearly
On Friday 13 March 2009 23:03:47 Chet Ramey wrote:
> Cameron Pulsford wrote:
> > I am running bash 4.0.10 (installed through macports)
> > hw = Macbook 2,1 os = mac os x 10.5.6
> > Compiled with gcc 4.0.1
> >
> > A lot of times after a long vim session when I return to bash, my cursor
> > is not on
On Fri, Mar 13, 2009 at 10:58 PM, Chet Ramey wrote:
> esum...@ualberta.ca wrote:
>
>> Machine Type: amd64-portbld-freebsd7.1
>>
>> Bash Version: 4.0
>> Patch Level: 10
>> Release Status: release
>>
>> Description:
>> Bash reports syntax error near unexpected token `)' for
>> new-style comm
