Re: variable assignments and parameter expansion in a single command

2007-03-26 Thread Kevin F. Quinn
On Sun, 25 Mar 2007 12:26:32 +0200 "Kevin F. Quinn" <[EMAIL PROTECTED]> wrote: > FWIW I tried also /usr/xpg4/bin/sh (with the Belenix livecd, SunOS > 5.11) and that shows the same as sh/ash/dash/bb. FI just tried on SunOS 5.8 (sparc) - a proper Sun installation - and /usr/xpg4/bin/sh there shows

bash-3.2 regression: command history display with coloured PS1.

2007-03-26 Thread Peter Volkov
Hello. The following bug (http://bugs.gentoo.org/172260) == Steps to reproduce: PS1="\e[36m[\e[34m\u\e[0m \e[32m\w\e[36m] \\$\e[0m " LC_ALL="en_US.UTF8" ls echo ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz Bash 3.1.* works correctl

Re: bash-3.2 regression: command history display with coloured PS1.

2007-03-26 Thread Andreas Schwab
Peter Volkov <[EMAIL PROTECTED]> writes: > Steps to reproduce: > PS1="\e[36m[\e[34m\u\e[0m \e[32m\w\e[36m] \\$\e[0m " This is broken. You need to bracket escape sequences with \[ \]. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürn

Re: bash-3.2 regression: command history display with coloured PS1.

2007-03-26 Thread Peter Volkov
On Пнд, 2007-03-26 at 17:35 +0200, Andreas Schwab wrote: > Peter Volkov <[EMAIL PROTECTED]> writes: > > Steps to reproduce: > > PS1="\e[36m[\e[34m\u\e[0m \e[32m\w\e[36m] \\$\e[0m " > > This is broken. You need to bracket escape sequences with \[ \]. Eh. Right. Sorry for noise. -- Peter. sign

Re: source(builtin) and read(2)

2007-03-26 Thread hooanon05
Andreas Schwab: > > When the file size is very large or the filesystem is poor, the read(2) > > systemcall may not read all of the file. In this case, the return value > > will be shorter than the requested bytes. > > Even worse, if read returns -1 then this writes beyond array bounds. > Also, fi