Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!ames!haven!ni.umd.edu!sayshell.umd.edu!louie
From: louie@sayshell.umd.edu (Louis A. Mamakos)
Newsgroups: comp.sys.next
Subject: Re: Keyboards
Message-ID: <1990Dec18.141803.14012@ni.umd.edu>
Date: 18 Dec 90 14:18:03 GMT
References: <59719@brunix.UUCP> <4538@media-lab.MEDIA.MIT.EDU> <Dec.18.03.10.19.1990.14075@remus.rutgers.edu>
Sender: usenet@ni.umd.edu (USENET News System)
Organization: University of Maryland, College Park
Lines: 24
Nntp-Posting-Host: sayshell.umd.edu

In article <Dec.18.03.10.19.1990.14075@remus.rutgers.edu>,
	 declan@remus.rutgers.edu (Declan McCullagh/LZ) writes:

>Also, in an earlier message, louie@sayshell.umd.edu (Louis A. Mamakos)
>complained about the new layout of the keyboard.  It's very painless
>to remap the keyboard in 2.0 - just drag the key symbol to the correct
>place on the keyboard.  In fact, my keyboard right now is mapped to
>Control-] (BracketRight) = | (Bar).

Of course this solution is less than optimal if you like to use
telnet, because control-] is the default telnet escape character.  I
think keyboard remapping is wonderful; it just wish they had left the
key in place.

The keyboard wasn't broke; it didn't need fixing.  My original cube's
keyboard has worked fine since we received the machine after it was
announced.

NeXT could have expended effort to put better quality microswitches in
the mouse instead if they felt compelled to change the user interface
hardware; I find that the left mouse button on my Cube's mouse bounces
quite a bit now.  Anyone else experience this problem?

louie