MIME-Version: 1.0
In-Reply-To: <4BCA93C4.5000904@bopp.net>
References: <d2b8c7b517c01.4bc9c651@shaw.ca> <4BCA1D1A.6050904@bopp.net> 	 <i2i416096c61004172139kd811372ek159da8d3c61074c8@mail.gmail.com> 	 <4BCA93C4.5000904@bopp.net>
Date: Sun, 18 Apr 2010 16:48:46 +0100
Message-ID: <u2o416096c61004180848l64d2ae47r433b3fa43cc7ab4d@mail.gmail.com>
Subject: Re: bash/readline spinout in vi command mode
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Jeremy Bopp:
>> When you say spin out, do you mean it's fully loading a core? That
>> would obviously be a bug, but I don't see that. For me, both with
>> ESC-; and Shift-F12 it's just sitting there waiting for more input,
>> which to me looks like normal operation because I do know that the
>> escape character at the start of both of those takes vi into command
>> mode and I've got no idea what either ';' or '[24;2~' might mean in
>> command mode. In both cases, pressing Enter a couple of time produces
>> a new prompt.
>
> Yes, it fully loads a core. =C2=A0What's strange is that if I hit ESC-F
> before the first time I hit ESC-; in a new shell session the problem is
> avoided. =C2=A0From what I read at http://linux.die.net/man/3/readline, t=
he
> key binding for both F and ; in command mode should be vi-char-search,
> so I'm not sure what the difference is between the two bindings.
>
> I get the same behavior under a Windows terminal running bash as well.
> I repeated all the tests both with and without my .inputrc file, minimal
> as it is, and got the same results every time.
>
> On a whim I also tried this in irb, which is the only other program I
> frequently use which I know uses libreadline, but I could not reproduce
> the problem.
>
> If there is any other information I can provide, let me know what it is.
> =C2=A0My system is a fairly vanilla XP installation which I updated to the
> latest packages earlier today.

Spinning on a 32-bit XP here as well, whereas it didn't on a 64-bit Win7.

Andy

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple