X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Thorsten Kampe Subject: Re: Shift-Tab for Backwards Completion Date: Wed, 18 Jun 2008 22:12:43 +0200 Lines: 24 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit User-Agent: MicroPlanet-Gravity/2.70.2067 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 * Frank Jacobs (Tue, 17 Jun 2008 14:49:18 -0500) > I've used the solution below so that I can go back in the completion > list in Bash via the SHIFT-TAB keystroke. However, I can only get it > to work when running in an xterm window (where $TERM=xterm). It > doesn't work in the plain-ol' Windows console window (where > $TERM=cygwin). > > The research that I've done has pointed me to termcap as a possible > suspect. Grokking termcap is going to take me a while. Before I go > down a possible dead end, does anyone have any comments on why > SHIFT-TAB doesn't work when running Cygwin/Bash in a Windows console > window? (By "doesn't work" I mean that SHIFT-TAB behaves the same as > pressing TAB by itself). Because Windows Console returns the same keycode for shifted/unshifted and for the Ctrl key. You can easily test that with [Ctrl][V] or "od - c" (which are the standards tools to find out the key codes to be able to assign actions to them). This is not restricted to the Windows console. Console[1] and the Linux console behave the same. Thorsten [1] http://console.sourceforge.net/ -- 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/