X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <416096c60908020148n6fc39e63h8e03f7ee5e24f58d@mail.gmail.com> References: <416096c60908020148n6fc39e63h8e03f7ee5e24f58d AT mail DOT gmail DOT com> Date: Sun, 2 Aug 2009 09:22:59 -0400 Message-ID: Subject: Re: [1.7] bash loop and mintty hung issue From: "Mark J. Reed" To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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 =C2=A0out 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 happe= n to you with set -o vi and pressing shift PF key when using mintty in cygw= in? > > 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: =C2=A0 =C2=A0 =C2=A0 http://cygwin.com/problems.html > FAQ: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 http:= //cygwin.com/faq/ > Documentation: =C2=A0 =C2=A0 =C2=A0 =C2=A0 http://cygwin.com/docs.html > Unsubscribe info: =C2=A0 =C2=A0 =C2=A0http://cygwin.com/ml/#unsubscribe-s= imple > > --=20 Mark J. Reed -- 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