X-Spam-Check-By: sourceware.org Message-ID: <4525605C.4070104@case.edu> Date: Thu, 05 Oct 2006 15:43:24 -0400 From: Chet Ramey Reply-To: chet DOT ramey AT case DOT edu User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909) MIME-Version: 1.0 To: cygwin AT cygwin DOT com, bash-testers AT case DOT edu CC: Eric Blake , chet AT case DOT edu Subject: Re: [bash-testers] Re: readline-5.2-1 prompt issue on cygwin References: <45247062 DOT 9000603 AT byu DOT net> <45247465 DOT 3090407 AT case DOT edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Igor Peshansky wrote: > 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 < ><^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 also cannot reproduce it with the bash-3.2 release candidate on Linux (aterm or xterm) or FreeBSD6 (aterm or xterm). I used the UTF-8 locale to activate the multibyte locale code, which seems to be where most of the display issues are. Otherwise, that detail is unimportant. Sorry I can't reproduce this particular issue, but it looks like the prompt string you sent will be valuable in checking whether or not the multiple-prompt-string-redraws problem has been solved. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Live Strong. No day but today. Chet Ramey, ITS, CWRU chet AT case DOT edu http://cnswww.cns.cwru.edu/~chet/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/