delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-1.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SARE_MSGID_LONG45,T_TO_NO_BRKTS_FREEMAIL |
X-Spam-Check-By: | sourceware.org |
MIME-Version: | 1.0 |
In-Reply-To: | <d258a5a011551.4bc9bd6e@shaw.ca> |
References: | <d258a5a011551 DOT 4bc9bd6e AT shaw DOT ca> |
Date: | Sat, 17 Apr 2010 21:15:12 +0100 |
Message-ID: | <k2u416096c61004171315v43d282abxb094ad335979f296@mail.gmail.com> |
Subject: | Re: bash loop using mintty |
From: | Andy Koppe <andy DOT koppe AT gmail DOT com> |
To: | cygwin AT cygwin DOT com |
X-IsSubscribed: | yes |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
ERIC HO wrote: > I reported a couple of times of the bash loop problem before. But it seem= s the problem could bot be duplicated > by others. > I use "mintty -" to start up a terminal session. > Today, I found out the problem. The loop is caused by set -o vi in my .ba= shrc. After I removed that statement, > =C2=A0I can hit =C2=A0shift F12 without bash looping (reported by task ma= nager). > If I start mintty without -, shift F12 just gives 4;2~ =C2=A0back. > Once I enter set -o vi, shift F12 hang and bash starts looping > With this information, I hope mintty users can duplicate this problem and= hopefully a fix could be available. That would be a bash/readline problem, not a mintty problem. Shift+F12 in mintty sends the same keycode that xterm sends: '\e[24;2~'. I suspect though that it is simply a case of vi mode interpreting that keycode in some vi-ish way. A vi expert will have to pronounce on that. 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |