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: References: Date: Sat, 1 Aug 2009 20:27:23 +0100 Message-ID: <416096c60908011227v8cfa574i3deadabb8d682a3e@mail.gmail.com> Subject: Re: [1.7] bash loop and mintty hung issue From: Andy Koppe 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 2009/8/1 ERIC HO: > Hi Andy, yes the same happens in xterm. =C2=A0I found out the cause of th= e problem. I have the following statement in my .bashrc: > set -o vi > > Not sure why this would casue the problem of using =C2=A0shift PF key and= causing terminal hung and bash looping. Sounds like a bug to me, or at least a very unfortunate feature. Might be worth reporting to gnu.bash.bug. Does anyone know what [24;2~ might mean in vi mode? 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