From xemacs-m  Sun Feb 23 03:08:43 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id DAA09343
	for <xemacs-beta@xemacs.org>; Sun, 23 Feb 1997 03:08:42 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQcecq01186; Sun, 23 Feb 1997 04:08:42 -0500 (EST)
Date: Sun, 23 Feb 1997 04:08:42 -0500 (EST)
Message-Id: <QQcecq01186.199702230908@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: Re: kp_ keysyms don't bind
In-Reply-To: <kiglo8f9a4v.fsf@jagor.srce.hr>
References: <199702230220.VAA18790@blight.IntraNet.com>
	<m2afowb5lf.fsf@altair.xemacs.org>
	<kiglo8f9a4v.fsf@jagor.srce.hr>

Hrvoje Niksic writes:
 > Steven L Baur <steve@miranova.com> writes:
 > 
 > > Jonathan Edwards writes:
 > > > In 19.15b95 keysyms of the form kp_0 are not being bound.
 > > > global-set-key accepts them, but the kp_0 key does not in fact get
 > > > bound (and is reported as the kp-0 key).
 > > 
 > > So far so good, this is intended.  The obsolete usage of
 > > kp_... etc. has been replaced by the more compatible kp-... notation.
 > > The underscore notation is accepted and silently converted to the
 > > minus sign for backwards compatibility.
 > 
 > No, Jonathan says that kp_0 doesn't get bound *at all*.  Like, you do:
 > 
 > (global-set-key [kp_0] 'foo)
 > 
 > And pressing kp_0 does nothing.

I tried the above example, pressed 0 on the keypad and got

Symbol's funtion definition is void: foo

So the translation magic works here.

