X-Recipient: archive-cygwin@delorie.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.4020805@cornell.edu> 	 <2377ADF68DFE455199B53E97E5747E43@HEPNTLTIM3> 	 <4A1B17FD.902@dronecode.org.uk> <4A1BD971.70808@cornell.edu> 	 <83bppfskbt.fsf@gnu.org> <4A1C5831.6030008@cornell.edu> 	 <99716858969849F89D65A4015B9948F7@HEPNTLTIM3> 	 <4A1C9952.8040100@cornell.edu> 	 <AECBDC9D8B31450CA07DD85A423AD033@dc.pp.rl.ac.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.koppe@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.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/

