Message-ID: <496EC898.1090504@gmail.com>
Date: Thu, 15 Jan 2009 05:24:40 +0000
From: Andy Koppe <andy.koppe@gmail.com>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: keycodes (was: Re: First Pass at mintty documentation; etc.)
References: <496A5EDE.9010204@veritech.com> <496A7038.402@gmail.com> <496B7C25.3090705@veritech.com> <496E528D.1090801@gmail.com> <gkm9u9$qp2$1@ger.gmane.org>
In-Reply-To: <gkm9u9$qp2$1@ger.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Andrew DeFaria wrote:
>>>  > "\e[1;5A": history-search-backward
>>>  > "\e[1;5B": history-search-forward
>>>
>>> Perhaps I don't understand this 'bash' feature, but it doesn't seem 
>>> to work for me.
>> Start typing a command, press Ctrl-Up, and it finds the previous line 
>> in the history that started like that.
> 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...

Yes, obviously you can bind the history search to any key you like.

To do the same as above with rxvt:

   "\eOa": history-search-backward
   "\eOb": history-search-forward

Speaking of history, does anyone know why xterm and rxvt diverged so 
much on modifier keycodes and why the xterm codes ended up being six 
characters long?

Andy

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