This is the mail archive of the
mailing list for the Cygwin project.
Re: [bash-testers] Re: readline-5.2-1 prompt issue on cygwin
- From: Igor Peshansky <pechtcha at cs dot nyu dot edu>
- To: Chet Ramey <chet dot ramey at case dot edu>
- Cc: bash-testers at case dot edu, Eric Blake <ebb9 at byu dot net>, cygwin at cygwin dot com, chet at case dot edu
- Date: Thu, 5 Oct 2006 09:14:41 -0400 (EDT)
- Subject: Re: [bash-testers] Re: readline-5.2-1 prompt issue on cygwin
- References: <announce.4523B5DB.firstname.lastname@example.org> <Pine.GSO.email@example.com> <firstname.lastname@example.org> <email@example.com>
- Reply-to: cygwin at cygwin dot com, bash-testers at case dot edu
On Wed, 4 Oct 2006, Chet Ramey wrote:
> Eric Blake wrote:
> > According to Igor Peshansky on 10/4/2006 9:03 AM:
> >>> The upstream maintainer claims that this version fixes some prompt display
> >>> bugs when using non-printing escape sequences with a single-line prompt.
> >>> I have not verified this, but hope that this is the case.
> >> FWIW, still doesn't work for me:
> >> $ export PS1='[\[\e[32m\]\h\[\e[0m\]:\[\e[33m\]\w\[\e[0m\]] \[\]'
> >> [helios:~] cd /c^L
> >> [helios:~] cd /c/c
> >> ^^^^^^^
> >> This is what's displayed. Removing the '\[\]' at the end doesn't help.
> >> Igor
> > I am able to confirm this. Using the above PS1 (the export is optional,
> > as it only has to be a shell variable rather than an environment
> > variable), and the xterm-unicode terminal as compiled for cygwin, along
> > with bash 3.1.17 and release candidate readline 5.2, I get the following
> > behavior when I type <c><d>< ></><c><^L>, where _ is the location of the
> > cursor:
> I can't reproduce it on Mac OS X using Terminal or xterm, using a UTF-8
> locale and the included prompt string. I will look at it on some other
> systems tomorrow.
FWIW, it's happening in an xterm under Cygwin as well, so it's not the
"cygwin" terminfo/termcap entry. Cygwin's xterm does not support UTF-8.
> (I can't tell from the description, but I assume that the ^L is followed
> by a screen clear. It's supposed to.)
Yes, it was. Since ^L behaves properly, I neglected to mention that.
> > I'm really at a loss as to how to go about debugging this, and don't
> > know whether the bug is in readline or in cygwin's terminal
> > descriptions. I haven't yet built bash 3.2 for cygwin; is there any
> > chance that bash-3.2 is using some readline hooks that bash 3.1 was
> > not using, such that this problem would go away?
> It's not. There are no readline hooks to use.
> > This appears to be the same bug that I have been repeatedly reporting:
> > http://lists.gnu.org/archive/html/bug-bash/2006-05/msg00023.html
> > http://lists.gnu.org/archive/html/bug-bash/2006-03/msg00005.html
> > http://lists.gnu.org/archive/html/bug-bash/2005-07/msg00115.html
> > Any hints on what I should try from within a debugger?
> Attach to it from another terminal and set breakpoints in
Please let me know if I can provide more input.
|\ _,,,---,,_ firstname.lastname@example.org | email@example.com
ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
|,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html