To: cygwin@cygwin.com
From: Andrew DeFaria <Andrew@DeFaria.com>
Subject:  Re: keycodes
Date:  Wed, 14 Jan 2009 23:05:42 -0700
Lines: 22
Message-ID: <gkmjno$h62$2@ger.gmane.org>
References:  <496A5EDE.9010204@veritech.com> <496A7038.402@gmail.com> <496B7C25.3090705@veritech.com> <496E528D.1090801@gmail.com> <gkm9u9$qp2$1@ger.gmane.org> <496EC898.1090504@gmail.com>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding:  7bit
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
In-Reply-To: <496EC898.1090504@gmail.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Andy Koppe wrote:
> 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.
The points were, since you seemed to have missed them, that 1) that's 
the default binding for bash and 2) it doesn't require MinTTY, nor 
xterm, nor any particular terminal emulator. IOW it works out of the 
box, in fact works in Cygwin's bash Windows console window and does not 
even restrict you to locating only the start of a command. All win, win, 
win situations as I see it.
-- 
Andrew DeFaria <http://defaria.com>
It's not hard to meet expenses, they're everywhere.


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