Re: exit somtimes not exit's the script

2006-01-23 Thread Paul Jarc
[EMAIL PROTECTED] wrote: > a exit inside a loop inside a pipe exits's the loop and not the > script. may bee a error. This is normal. Each element of a pipeline is run in a child process. paul ___ Bug-bash mailing list Bug-bash@gnu.org h

Re: Possible bash bug when dealing with CR/LF in variable expansion

2006-01-23 Thread Paul Jarc
"Johannes Thoma" <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED]:~/bash/bash-3.1$ zak=`printf '\x0d\x0a'` As documented in the man page under "Command Substitution", this strips off any trailing newlines from the program's output before assigning the variable's value. So zak contains only a carria

Botched assertion in malloc]

2006-01-23 Thread paul
CConfiguration Information [Automatically generated, do not change]: Machine: i386 OS: linux-gnu Compiler: i386-redhat-linux-gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-redhat-linux-gnu' -DCONF_VENDOR='redhat' -DSHELL -DHAVE_CON

behavior diff. btw. 3.0 and 3.1 (may be a bug)

2006-01-23 Thread vw
Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba

patch for support of $DATE and $DATEFORMAT

2006-01-23 Thread fraff
Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTY PE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/local/share/locale' -DPACK

exit somtimes not exit's the script

2006-01-23 Thread vw
Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba

Error in Bash Reference Manual

2006-01-23 Thread Anders Brandén
___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

Possible bash bug when dealing with CR/LF in variable expansion

2006-01-23 Thread Johannes Thoma
From: johannes To: bug-bash@gnu.org,[EMAIL PROTECTED] Subject: [50 character or so descriptive subject here (for reference)] Configuration Information [Automatically generated, do not change]: Machine: i386 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -D

whole line echoed every char I type

2006-01-23 Thread Dan Jacobson
Holy moly, without LC_ALL=C, for every character I type, the whole line is echoed! 03:39 ~$ LC_ALL=C script Script started, file is typescript 03:39 ~$ exit Script done, file is typescript 03:39 ~$ cat -v typescript Script started on Tue Jan 24 03:39:46 2006 ^[[01;35m03:39 ~$^[[00m exit^M Script

Re: can't expand after colon

2006-01-23 Thread Chet Ramey
> Must one use \: to make this work? Yes. Or take `:' out of $COMP_WORDBREAKS. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet ) Live Strong. Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http:

Re: can't expand after colon

2006-01-23 Thread Paul Jarc
Dan Jacobson <[EMAIL PROTECTED]> wrote: > Must one use \: to make this work? That, or adjust $COMP_WORDBREAKS to not include ":". paul ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

can't expand after colon

2006-01-23 Thread Dan Jacobson
Must one use \: to make this work? $ cd /tmp/jidanni.org jidanni.org/ jidanni.org:2082/ $ cd /tmp/jidanni.org: Display all 456 possibilities? (y or n) ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash