MIME-Version: 1.0
In-Reply-To: <4A1E7C50.8020505@cornell.edu>
References: <4A168F2B.4020805@cornell.edu> <4A1BD971.70808@cornell.edu> 	 <83bppfskbt.fsf@gnu.org> <4A1C5831.6030008@cornell.edu> 	 <99716858969849F89D65A4015B9948F7@HEPNTLTIM3> 	 <4A1C9952.8040100@cornell.edu> 	 <AECBDC9D8B31450CA07DD85A423AD033@dc.pp.rl.ac.uk> 	 <4A1D9D05.40407@cornell.edu> <838wkhsm5e.fsf@gnu.org> 	 <4A1E7C50.8020505@cornell.edu>
Date: Thu, 28 May 2009 15:02:35 +0100
Message-ID: <416096c60905280702m6e4cb748ic305be3592d81c70@mail.gmail.com>
Subject: Re: emacs -nw keypad, tpu-edt.el, and C-h
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Ken Brown:
> A separate issue that has arisen in this thread is that when emacs runs
> in a cygwin terminal [*], it sees C-h as DEL instead of as the help key.
> Can someone familiar with cygwin terminals help with this? =C2=A0I'm spec=
ulating
> again (bad habit), but it seems that the keycodes are being processed bef=
ore
> they reach emacs, so that C-h becomes indistinguishable from the Backspace
> key.

Careful, you're straying into a pseudo-religious warzone here. :)

There's an ancient and pointless argument about whether the Backspace
key should send ^H (0x08) or ^? (0x7F). See here for the whole sorry
saga:

http://www.ibb.net/~anne/keyboard.html

Inevitably, Linux distributions are split on this issue, with Debian
using ^? and Redhat using ^H. Cygwin is in the ^H camp, i.e. all its
terminals send ^H by default. xterm, rxvt, and mintty can be
configured to send ^? instead though, which, as you note, is
particular useful with emacs as it leaves Ctrl+H available as the help
shortcut.

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/