Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!cunixf.cc.columbia.edu!howie
From: howie@cunixf.cc.columbia.edu (Howie Kaye)
Newsgroups: comp.sys.next
Subject: Re: XNeXT on NextStep 2.0?????
Keywords: XNeXT, Mouse-X
Message-ID: <1991Mar10.194332.28445@cunixf.cc.columbia.edu>
Date: 10 Mar 91 19:43:32 GMT
References: <1991Mar5.232508.20719@msuinfo.cl.msu.edu> <1991Mar10.000354.15364@cunixf.cc.columbia.edu> <1991Mar10.121059.18635@thunder.mcrcim.mcgill.edu>
Reply-To: howie@cunixf.cc.columbia.edu (Howie Kaye)
Organization: Columbia University
Lines: 17

In article <1991Mar10.121059.18635@thunder.mcrcim.mcgill.edu> mouse@thunder.mcrcim.mcgill.edu (der Mouse) writes:

>> and have had a couple of minor reports about it (like the shifted top
>> row of the new keyboard's keypad aren't supported).
>
>Any idea how to find out what sort of keyboard is in use?  It's just a
>matter of xmodmap to fix this, but it *should* be dealt with
>automatically - and if I can sense the keyboard type, it will be.
>
>					der Mouse


I just put up a new (split) version on cunixf.  Someone complained
that a 12M file transfer wasn't working out.  I also made the code
always put in the shifted versions of the top row keypad on new keyboards.

/h