Escape in vi mode just takes you into edit mode; [ is the first character in any of a bunch of "go to the start of some group" sequences, but 2 isn't a valid continuation of any of those, so it has no effect and the 24 is entered as a repeat count. ; searches forward on the line for the last character looked for with the (f)ind command.
And that's the problem - you can reproduce it by just hitting Esc and then semicolon. If you've previously entered any (f)ind command, it's fine, but if you haven't, it locks up; someone missed a degenerate case in the last readline update. On Sun, Aug 2, 2009 at 4:48 AM, Andy Koppe wrote: > 2009/8/2 ERIC HO: >> Hi Andy, FYI. I have tested out on my Linux machine running bash 3.2.48 >> (instead of 3.2.49 as on cygwin). I don't have this problem with bash >> undxterm with set -o vi and pressing shift PF key. Does this problem happen >> to you with set -o vi and pressing shift PF key when using mintty in cygwin? > > Yep, both in mintty and xterm. And actually I can reproduce it in the > Cygwin console too, by entering the offending keycode manually. After > pressing 'Escape [ 2 4', the prompt looks like this: > > (arg: 24) > > Pressing ';' at this point causes bash to hang. > > The issue only shows up on Cygwin 1.7, not 1.5. Since their bash > versions are almost identical, I'd suspect it's to do with the newer > readline on 1.7. > > 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 > > -- Mark J. Reed <markjr...@gmail.com> -- 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
