X-Recipient: archive-cygwin@delorie.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: References: Date: Sun, 2 Aug 2009 09:48:08 +0100 Message-ID: <416096c60908020148n6fc39e63h8e03f7ee5e24f58d@mail.gmail.com> Subject: Re: [1.7] bash loop and mintty hung issue From: Andy Koppe To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 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 = under xterm with set -o vi and pressing shift PF key. Does this problem hap= pen to you with set -o vi and pressing shift PF key when using mintty in cy= gwin? 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