X-Spam-Check-By:	sourceware.org
Message-ID:	<43E9E951.5070106@byu.net>
Date:	Wed, 08 Feb 2006 05:51:29 -0700
From:	Eric Blake <ebb9 AT byu DOT net>
User-Agent:	Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version:	1.0
To:	Zach Gelnett <zachg99 AT gmail DOT com>
CC:	cygwin AT cygwin DOT com
Subject:	Re: Prompt issue within cygwin
References:	<f894c8ac0602060655wcca2b4n9b42ca7dca107703 AT mail DOT gmail DOT com>
In-Reply-To:	<f894c8ac0602060655wcca2b4n9b42ca7dca107703@mail.gmail.com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

According to Zach Gelnett on 2/6/2006 7:55 AM:
>>Chet Ramey, the upstream readline maintainer, FINALLY admitted that his
>>routines have display bugs when readline is compiled with multi-byte
>>support, and when a single-line prompt contains invisible characters.

> Interesting, so, based on my reading of this, if i were to recompile
> readline without multi-byte support it should resolve this problem?

Others have reported on this list that using --disable-multibyte when
configuring readline fixes bash prompts.  However, I am reluctant to do
that for the official cygwin release, as I am not sure who might be
relying on multibyte readline behavior.

-- 
Life is short - so eat dessert first!

Eric Blake             ebb9 AT byu DOT net
volunteer cygwin readline maintainer

--
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/

- Raw text -