Re: incorrect handling of invisible characters in prompt string

2006-05-05 Thread Chet Ramey
Mike Frysinger wrote: > to dig up this thread yet again :) > http://lists.gnu.org/archive/html/bug-bash/2006-03/msg6.html > > a user reported this with bash-3.0.17 with a good test case: > http://bugs.gentoo.org/130955 > > and i'm able to reproduce this here by setting my PS1: > PS1='$(echo "

Re: incorrect handling of invisible characters in prompt string

2006-05-03 Thread Mike Frysinger
On Wednesday 03 May 2006 21:42, Mike Frysinger wrote: > the proposed hack: > http://lists.gnu.org/archive/html/bug-bash/2006-03/msg5.html > > seems to work for this test case ... but then seems to break another one: export LC_ALL=C PS1='\[\e[0;33m\]\u\[\e[0m\] ' printf a > foo.txt cat foo.txt

Re: incorrect handling of invisible characters in prompt string

2006-05-03 Thread Mike Frysinger
to dig up this thread yet again :) http://lists.gnu.org/archive/html/bug-bash/2006-03/msg6.html a user reported this with bash-3.0.17 with a good test case: http://bugs.gentoo.org/130955 and i'm able to reproduce this here by setting my PS1: PS1='$(echo "Strange \[\e[0;32m\]Prompt\[\e[0m\] ")

Re: incorrect handling of invisible characters in prompt string

2006-03-04 Thread Chet Ramey
Eric Blake wrote: > [Please use mailing lists instead of sending private mail > to random developers - I don't know whether you > intended this as a question about bash proper or > about the cygwin port of bash, so I have cross-posted > my reply] > >> Hi Eric, >> >> I found the following message (

Re: incorrect handling of invisible characters in prompt string

2006-03-03 Thread Eric Blake
[Please use mailing lists instead of sending private mail to random developers - I don't know whether you intended this as a question about bash proper or about the cygwin port of bash, so I have cross-posted my reply] > Hi Eric, > > I found the following message (from July 2005) by you on the cy

Re: incorrect handling of invisible characters in prompt string

2005-07-14 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This bug is insidious, as there is more than one wrong string printed to the display. For example, this screenshot shows that the original prompt doubles the last prompt character ($), but after tab completion has displayed a list, it doubles the firs

incorrect handling of invisible characters in prompt string

2005-07-12 Thread Thomas Dickey
Configuration Information [Automatically generated, do not change]: Machine: i386 OS: netbsdelf Compiler: cc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='netbsdelf' -DCONF_MACHTYPE='i386--netbsdelf' -DCONF_VENDOR='' -DLOCALEDIR='/usr/pkg/share/locale' -DPACKAGE='bas