X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <496EC898.1090504@gmail.com> Date: Thu, 15 Jan 2009 05:24:40 +0000 From: Andy Koppe User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: keycodes (was: Re: First Pass at mintty documentation; etc.) 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> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT 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/