Bash-4.0 Official Patch 11

2009-04-07 Thread Chet Ramey
BASH PATCH REPORT = Bash-Release: 4.0 Patch-ID: bash40-011 Bug-Reported-by:Matt Zyzik n Bug-Reference-ID: <20090312015018.c0074138...@ice.filescope.com> Bug-Reference-URL: http://lists.gnu.org/ar

Bash-4.0 Official Patch 12

2009-04-07 Thread Chet Ramey
BASH PATCH REPORT = Bash-Release: 4.0 Patch-ID: bash40-012 Bug-Reported-by:"Clark J. Wang" Bug-Reference-ID: Bug-Reference-URL: http://lists.gnu.org/archive/html/bug-bash/2009-03/msg00129.html

Bash-4.0 Official Patch 15

2009-04-07 Thread Chet Ramey
BASH PATCH REPORT = Bash-Release: 4.0 Patch-ID: bash40-015 Bug-Reported-by:Lubomir Rintel Bug-Reference-ID: <1237654931.32737.13.ca...@localhost.localdomain> Bug-Reference-URL: http://lists.gnu.

Bash-4.0 Official Patch 14

2009-04-07 Thread Chet Ramey
BASH PATCH REPORT = Bash-Release: 4.0 Patch-ID: bash40-014 Bug-Reported-by:small...@gmail.com Bug-Reference-ID: <49c460fe.40...@gmail.com> Bug-Reference-URL: http://lists.gnu.org/archive/html/bug

Bash-4.0 Official Patch 13

2009-04-07 Thread Chet Ramey
BASH PATCH REPORT = Bash-Release: 4.0 Patch-ID: bash40-013 Bug-Reported-by:jida...@jidanni.org Bug-Reference-ID: Bug-Reference-URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519165 Bug-Descripti

Bash-4.0 Official Patch 17

2009-04-07 Thread Chet Ramey
BASH PATCH REPORT = Bash-Release: 4.0 Patch-ID: bash40-017 Bug-Reported-by:Lubomir Rintel Bug-Reference-ID: <1237654931.32737.13.ca...@localhost.localdomain> Bug-Reference-URL: http://lists.gnu.

Bash-4.0 Official Patch 16

2009-04-07 Thread Chet Ramey
BASH PATCH REPORT = Bash-Release: 4.0 Patch-ID: bash40-016 Bug-Reported-by:Brian J. Murrell" Bug-Reference-ID: <1237564627.7666.12.ca...@pc.interlinx.bc.ca> Bug-Reference-URL:http://lists.gnu.org/arch

Misleading syntax in manual

2009-04-07 Thread Reuben Thomas
The syntax for the "for" command is misleading, as although correct for bash, it is not POSIX-compliant. I am using GNU bash, version 3.2.48(1)-release (i486-pc-linux-gnu) The man page says: for name [ in word ] ; do list ; done which conflicts with the POSIX syntax definition, given in http

Bash 4 cursor in my prompt

2009-04-07 Thread Special Sauce
From: anton To: bug-bash@gnu.org Subject: Cursor starts inside prompt Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' - DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-un

Re: Bash 4 cursor in my prompt

2009-04-07 Thread Mike Frysinger
On Tuesday 07 April 2009 15:10:16 Special Sauce wrote: > From: anton > To: bug-bash@gnu.org > Subject: Cursor starts inside prompt > > Configuration Information [Automatically generated, do not change]: > Machine: x86_64 > OS: linux-gnu > Compiler: gcc > Compilation CFLAGS: -DPROGRAM='bash' -DCONF

Re: set -x prejudiced; won't smell UTF-8 coffee

2009-04-07 Thread Mike Frysinger
On Monday 06 April 2009 22:03:28 jida...@jidanni.org wrote: > Mike Frysinger writes: > > exactly do you suggest differentiating... > > I don't know. It's all truly over my head. > All I know is "how are you going to 'market' this stuff in Asia?". we dont "market" anything. either you use it and

Re: set -x prejudiced; won't smell UTF-8 coffee

2009-04-07 Thread jidanni
Instead of having bash make judgements about what people want from their personal mix of: $ locale|sed 's/.*=//;s/"//g;/^$/d'|sort|uniq -c 2 C 11 zh_TW.UTF-8 instead just have a passthru option they could enable, that says "I hereby agree that I want to be sent raw -x output back, and if

Re: Bash 4 cursor in my prompt

2009-04-07 Thread Special Sauce
On Apr 8, 12:08 am, Mike Frysinger wrote: > On Tuesday 07 April 2009 15:10:16 Special Sauce wrote: > > > > > From: anton > > To: bug-b...@gnu.org > > Subject: Cursor starts inside prompt > > > Configuration Information [Automatically generated, do not change]: > > Machine: x86_64 > > OS: linux-gnu

Re: Bash 4 cursor in my prompt

2009-04-07 Thread Ian Kelling
Mike Frysinger wrote: considering it seems to involve the prompt, you really need to post your exact prompt settings (i.e. PS1/PS2/etc...) -mike Realize that in PS vars, \[ and \] should be used around non-printable characters. This surely won't happen if you start with --norc. You've got to

Re: set -x prejudiced; won't smell UTF-8 coffee

2009-04-07 Thread Mike Frysinger
On Wednesday 08 April 2009 02:29:17 jida...@jidanni.org wrote: > Instead of having bash make judgements about what people want from their > personal mix of: > $ locale|sed 's/.*=//;s/"//g;/^$/d'|sort|uniq -c > 2 C > 11 zh_TW.UTF-8 locale variables have pretty clear definitions. obvious

Re: Bash 4 cursor in my prompt

2009-04-07 Thread Ian Kelling
Special Sauce wrote: [an...@nobby-nobbs ~]$ echo $PS1 [\[\e[28;1m\...@\h\[ \e[0m\]\w]$ [an...@nobby-nobbs ~]$ echo $PS2 Work fine with the bash in the ubuntu repos I put this at the end of my .bashrc and it works fine for me. PS1='[\[\e[28;1m\...@\h\[ \e[0m\]\w]$ ' Theres probably something e

Re: Bash 4 cursor in my prompt

2009-04-07 Thread Mike Frysinger
and what `locale` settings you're using -mike signature.asc Description: This is a digitally signed message part.