public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Mark J. Reed" <markjreed@gmail.com>
To: cygwin@cygwin.com
Subject: Re: First Pass at mintty documentation; etc.
Date: Thu, 15 Jan 2009 05:44:00 -0000	[thread overview]
Message-ID: <f60fe000901141952x55eca979ue7af914c84a010bd@mail.gmail.com> (raw)
In-Reply-To: <gkm9u9$qp2$1@ger.gmane.org>

On Wed, Jan 14, 2009 at 10:18 PM, Andrew DeFaria wrote:
> Why not simply type Ctrl-R then the first few letters of a command (or some
> letters in the middle of a command). Works great! Requires no support from
> any terminal emulator...

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?  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.

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.

--
Mark J. Reed <markjreed@gmail.com>

--
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/

  reply	other threads:[~2009-01-15  3:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-11 21:39 First Pass at mintty documentation Lee D.Rothstein
2009-01-11 22:31 ` Andy Koppe
2009-01-11 23:03   ` Matt Wozniski
2009-01-12  4:30   ` Christopher Faylor
2009-01-12 18:25   ` First Pass at mintty documentation; etc Lee D. Rothstein
2009-01-14 23:37     ` Andy Koppe
2009-01-15  3:19       ` Andy Koppe
2009-01-15  6:03         ` console vs pty (was: Re: First Pass at mintty documentation; etc.) Andy Koppe
2009-01-15  6:54           ` Christopher Faylor
2009-01-16  6:55         ` First Pass at mintty documentation; etc Lee D. Rothstein
2009-01-16  9:57           ` Charles Wilson
2009-01-15  5:24       ` Andrew DeFaria
2009-01-15  5:44         ` Mark J. Reed [this message]
2009-01-15 12:34           ` Andrew DeFaria
2009-01-15 15:41             ` Mark J. Reed
2009-01-15  5:49         ` keycodes (was: Re: First Pass at mintty documentation; etc.) Andy Koppe
2009-01-15 12:43           ` keycodes Andrew DeFaria
2009-01-15 18:19             ` keycodes Matt Wozniski
2009-01-16 10:05               ` keycodes Andrew DeFaria
2009-01-15 15:51           ` keycodes (was: Re: First Pass at mintty documentation; etc.) Matt Wozniski
2009-01-16  5:20       ` First Pass at mintty documentation; etc Lee D. Rothstein
2009-01-16 13:52 Ashok Vadekar
2009-01-16 20:41 ` Lee D. Rothstein

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f60fe000901141952x55eca979ue7af914c84a010bd@mail.gmail.com \
    --to=markjreed@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).