X-Spam-Check-By:	sourceware.org
Message-ID:	<f894c8ac0602060655wcca2b4n9b42ca7dca107703@mail.gmail.com>
Date:	Mon, 6 Feb 2006 08:55:06 -0600
From:	Zach Gelnett <zachg99 AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Prompt issue within cygwin
MIME-Version:	1.0
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
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id k16EtHnK007767

>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.  The
>problem stems from the fact that there is no reliable way to determine
>which column the cursor is currently in, so readline makes some
>assumptions that the prompt always starts in column 0 (which is not always
>valid):
>
>http://lists.gnu.org/archive/html/bug-bash/2006-02/msg00018.html
>
>Hopefully Chet holds true to his promise and makes readline 5.2 better at
>this (although given the history of his past releases, it will be more
>than a year away; and he doesn't post his development version control
>system online, so the rest of the world is stuck waiting).

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

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