delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-2.3 required=5.0 tests=AWL,BARRACUDA_BRBL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS |
X-Spam-Check-By: | sourceware.org |
To: | cygwin AT cygwin DOT com |
From: | Andrew DeFaria <Andrew AT DeFaria DOT com> |
Subject: | Re: First Pass at mintty documentation; etc. |
Date: | Wed, 14 Jan 2009 23:02:53 -0700 |
Lines: | 28 |
Message-ID: | <gkmjif$h62$1@ger.gmane.org> |
References: | <496A5EDE DOT 9010204 AT veritech DOT com> <496A7038 DOT 402 AT gmail DOT com> <496B7C25 DOT 3090705 AT veritech DOT com> <496E528D DOT 1090801 AT gmail DOT com> <gkm9u9$qp2$1 AT ger DOT gmane DOT org> <f60fe000901141952x55eca979ue7af914c84a010bd AT mail DOT gmail DOT com> |
Mime-Version: | 1.0 |
User-Agent: | Thunderbird 2.0.0.19 (Windows/20081209) |
In-Reply-To: | <f60fe000901141952x55eca979ue7af914c84a010bd@mail.gmail.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 |
Mark J. Reed wrote: > True, but that's only one direction of history search, albeit the most > commonly useful one. For those cases where you're somewhere back in > your history and need to search forward, what do you do? In my 25 years of working on such systems I can probably count on 2 fingers the number of times such a situation has arose and what I did was Control-C then Control-R again. > The default binding for history-search-forward is control-S; > unfortunately, that's also usually the stop character and therefore > caught by the terminal before bash ever sees it. So you have to either > change the stop character or rebind the function, and if you rebind > that one you might as well bind the other one to something symmetric. Again, if the need were more than 2 times in 25 years I'd probably just bind Control-E to it or something like that. > Also, while it's fun to customize things in .inputrc (I have mine set > to editing-mode vi, in which incidentally the / key starts a history > search), I do recommend that everyone learn the emacs keys just > because that's what bash defaults to. Sure, if I'm going to be typing > more than a couple commands in a foreign bash setup, the first one I > type is "set -o vi". But for short sessions in someone else's > environment it's handy to be able to use the default bindings. Hmmm... My usual inclination is to type "set -o emacs" when required! ;-) Different strokes... -- Andrew DeFaria <http://defaria.com> What do you do when you see an endangered animal that eats only endangered plants? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |