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: Chet Ramey <chet dot ramey at case dot edu>
- To: bash-testers at case dot edu, Eric Blake <ebb9 at byu dot net>
- Cc: cygwin at cygwin dot com, chet at case dot edu
- Date: Wed, 04 Oct 2006 22:56:37 -0400
- Subject: Re: [bash-testers] Re: readline-5.2-1 prompt issue on cygwin
- References: <announce.4523B5DB.email@example.com> <Pine.GSO.firstname.lastname@example.org> <email@example.com>
- Reply-to: chet dot ramey at case dot edu
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.
> 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
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
(I can't tell from the description, but I assume that the ^L is followed
by a screen clear. It's supposed to.)
> 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:
> Any hints on what I should try from within a debugger?
Attach to it from another terminal and set breakpoints in
``The lyf so short, the craft so long to lerne.'' - Chaucer
Live Strong. No day but today.
Chet Ramey, ITS, CWRU firstname.lastname@example.org http://cnswww.cns.cwru.edu/~chet/
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html