This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: readline Bug! ;-) [was: Bash Bug! (was: Bug in rxvt 2.7.2 ...)]
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Thomas Mellman <tmellman at web dot de>
- Cc: cygwin at cygwin dot com
- Date: Thu, 10 Oct 2002 12:24:34 -0400 (EDT)
- Subject: Re: readline Bug! ;-) [was: Bash Bug! (was: Bug in rxvt 2.7.2 ...)]
- Reply-to: cygwin at cygwin dot com
On Thu, 10 Oct 2002, Thomas Mellman wrote:
> WRT <20021002125316.GB1604@tishler.net>,
>
> > I have been experiencing similar problems since upgrading to bash
> > 2.05b-2 and libreadline5 4.3-1. My typical problem is that the "c"
> > command as in "cw" (i.e., change word) would stop working, but "dw"
> > (i.e., delete word) followed by "i" (i.e., insert) was fine.
>
> I think I discovered something interesting about this: I believe it
> occurs after one uses a different vi feature that is also broken:
>
> The use of "." to repeat the last operation works intermittenly in
> CYGWIN readline, but I believe that if you use it and it doesn't do what
> it's supposed to, then the problem with the loss of functionality with
> the other commands stops working...
>
> Da - naturally, it could also be that there is an even earlier event
> that breaks not only the "." command but the other operations as
> well.... I don't know if there's any causation there - but I do believe
> there's a connection.
Yes, there is. This particular bug has apparently been fixed in the
latest version of readline. See one of my previous messages for the link
to the ftp site with the patches.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Water molecules expand as they grow warmer" (C) Popular Science, Oct'02, p.51
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/