Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!bcm!dimacs.rutgers.edu!seismo!uunet!orca!orca!bsteinke
From: bsteinke@dsd.es.com (Bruce Steinke)
Newsgroups: comp.windows.x
Subject: Re: Ncd keyboard num-lock
Message-ID: <1991Feb14.205124.3734@dsd.es.com>
Date: 14 Feb 91 20:51:24 GMT
References: <18034@memqa.uucp> <1991Feb12.193608.27897@convex.com> <18285@memqa.uucp> <52027@cornell.UUCP>
Sender: usenet@dsd.es.com
Reply-To: bsteinke@dsd.es.com (Bruce Steinke)
Organization: Evans & Sutherland Computer Corp., Salt Lake City, UT
Lines: 29
Nntp-Posting-Host: 130.187.100.100

In article <52027@cornell.UUCP>, parmelee@wayback.cs.cornell.edu (Larry Parmelee) writes:
> On the NCD keyboards, I don't believe you can use either of the lock
> keys as general purpose keys, due to the hardware design.

 [deleted stuff...] 

> -Larry Parmelee
> parmelee@cs.cornell.edu

I use an NCD, and I have no trouble redefining the Caps Lock key.

I use xev to determine the keycode, 17 on my system, an then put a line
in my .keymodrc which I execute using xmodmap. For example, the line in
.keymodrc is:

	keycode 17 = KP_F1

	xmodmap .keymodrc

Using xev again, I verify that the Caps Lock key generates a key press and
release (on the same stroke) and the LED does NOT come on. Also, the system
sees the key as keypad function key 1 (PF1 for those VT100 users).

-Bruce
-- 
  Bruce F. Steinke                  | "And the road goes ever on..."
  bsteinke@dsd.es.com               |  Bilbo Baggins
  Evans & Sutherland Computer Corp. |
  Salt Lake City, Utah              |  No moss under these feet!