Moving to cygwin-apps, as this is a packaging issue.
On Wed, 4 Oct 2006, Eric Blake wrote:
> Additionally, this version is not strictly binary compatible with
> readline 5.1; it removes a cygwin-specific entry point that bash 3.0
> (but not bash 3.1) depended on. Now that bash 3.0 is no longer
> available from the cygwin mirrors, I felt it safe to drop that
> cygwin-specific patch. Although it is unlikely that any other package
> depended on this entry point, I need to know now if this decision was
> not wise, in which case I will create libreadline7 when promoting
> readline 5.2 to current, leaving libreadline6 to preserve the entry
> point; but I will only do this if someone can demonstrate why it is
> needed (hint, you would have to mention the entry point by name to show
> you know what you are talking about).
It's usually a good idea to leave the compatibility library around in any
case (hint: someone may have linked their executable with that particular
version of libreadline, and would not be in a position to rebuild the
executable).
> 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
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ [EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
|,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"
