Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 11 Oct 2002 08:10:13 -0400 From: Jason Tishler Subject: Re: readline Bug! ;-) [was: Bash Bug! (was: Bug in rxvt 2.7.2 ...)] In-reply-to: <200210101230.g9ACUjX21786@mailgate5.cinetic.de> To: Thomas Mellman Cc: cygwin@cygwin.com Mail-followup-to: Thomas Mellman , cygwin@cygwin.com Message-id: <20021011121013.GC956@tishler.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.4i References: <200210101230.g9ACUjX21786@mailgate5.cinetic.de> Thomas, On Thu, Oct 10, 2002 at 02:30:46PM +0200, 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... Thanks for the above -- it seems to match my observations. I will (try to) avoid using the "." command until a patched bash is released. Jason -- 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/