X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<AECBDC9D8B31450CA07DD85A423AD033@dc.pp.rl.ac.uk>
References:	<4A168F2B DOT 4020805 AT cornell DOT edu> <2377ADF68DFE455199B53E97E5747E43 AT HEPNTLTIM3> <4A1B17FD DOT 902 AT dronecode DOT org DOT uk> <4A1BD971 DOT 70808 AT cornell DOT edu> <83bppfskbt DOT fsf AT gnu DOT org> <4A1C5831 DOT 6030008 AT cornell DOT edu> <99716858969849F89D65A4015B9948F7 AT HEPNTLTIM3> <4A1C9952 DOT 8040100 AT cornell DOT edu> <AECBDC9D8B31450CA07DD85A423AD033 AT dc DOT pp DOT rl DOT ac DOT uk>
Date:	Wed, 27 May 2009 20:56:21 +0100
Message-ID:	<416096c60905271256s359d1325g8d2ed3057c3950f3@mail.gmail.com>
Subject:	Re: emacs -nw keypad
From:	Andy Koppe <andy DOT koppe AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

> In an xterm (with TERM=xterm) a few keypad keys do in fact have a (not very
> useful) definition: kp-f1, kp-f2, kp-f3, kp-f4 are (incorrectly) mapped to f1,
> f2, f3, f4 and kp-enter is correctly mapped.

With xterm's default config, F1 to F4 do actually send the keypad
codes ^[OP to ^[OS. That's because the vt100 terminal had the keys PF1
to PF4 on the keypad, but it didn't have F keys like PC keyboards do.
Hence those mappings in emacs do make sense.

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/

- Raw text -