Path: utzoo!news-server.csri.toronto.edu!rutgers!usc!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!deccrl!news.crl.dec.com!jg
From: jg@crl.dec.com (Jim Gettys)
Newsgroups: comp.unix.ultrix
Subject: Re: Key repeat under X
Message-ID: <1991Mar12.212519.24326@crl.dec.com>
Date: 12 Mar 91 21:25:19 GMT
References: <1991Mar11.165600.3792@odin.diku.dk> <1991Mar12.125847.15278@crl.dec.com> <0brHrFb0BwwKI8lStO@transarc.com>
Sender: news@crl.dec.com (USENET News System)
Organization: DEC Cambridge Research Lab
Lines: 22

In article <0brHrFb0BwwKI8lStO@transarc.com>, Steve_Lammert@TRANSARC.COM writes:
> 
> Does this mean that the console on DECstations
> will also be getting a useful terminal type?
> 
If what you mean is the console's behavior before X is running, the answer is no.
I ran out of energy to do anything in this area, though I did redo how the keyboard
works pretty completely, to make it "do the right thing" according to the X protocol
spec within the limitations of what the current keyboard hardware will do.
(not to mention fixing long standing problems with hot swapping keyboards, for example).
(i.e. up/down while autorepeating will work, and per key control over autorepeat).
It would now be pretty easy to do, however, and the work would be able to be shared
among all the display types, which was never true of the old horrible, disgusting,
messes of Ultrix display drivers... I consider it the best form of progress to be
able to throw away code, which is what is now beginning to happen.  Nothing like
having less code to maintain, and less code to write for new displays, and less
problems with system configuration, as one server will run on multiple display types.

The other major feature is that it is much less work to deal with new display types,
which should make third party's lives very much easier when they want to do TURBOchannel
displays on our machines.
			- Jim