Prompt issue within cygwin

Zach Gelnett zachg99@gmail.com
Mon Feb 6 14:59:00 GMT 2006


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



More information about the Cygwin mailing list