Use of New Keyboards with ITS.

[John L. Kulp <JLK at MIT-MC>]

We are going to hook up a new kbd to the PTV system in the next few
days, and the obvious question comes up about how to encode all
the function keys.  I suppose they could be handled the way
they are on the old keyboard, namely send chars with the TOP bit +
100 + <code>.  In order to distinguish them from the old kbd,
how about encoding them in 140-177?  Presumably the extra modifier
bits (SUPER, HYPER, and GREEK) need to be allowed (that uses up
all the bits available in the intelligent terminal protocol, unless
we want to flush SHIFT and SHIFT-LOCK).  It doesn't much matter
what the encoding is, as long as its documented.  I guess any
part of the system which masks off the high modifier bits or
otherwise depends on them being zero will have to get looked at.

ITS presumably wants to know about the SYSTEM key (treat like BACK/NEXT).

Its about time DDT knew about CLEAR (or CLEAR INPUT on the new kbds) which
should behave like ^D.  Also, HELP, STOP OUTPUT (^S, actually this should
probably be defined to do an output hold at the terminal, followed by an
output reset from the remote process (as is currently done)), ABORT (^G), END
(^C), RESUME ($P), etc.

TELNET and SUPDUP should be informed about the NETWORK key.

Various programs should know about END, ABORT, RESUME, BREAK, QUOTE, HELP,
STATUS (I'm not saying every program in the world should be retrofitted
to know about these, but the basic ones -- DDT, TECO, LISP -- probably
should).

I suspect that not much is going to happen on this until AI TV's start
getting new keyboards, but I would at least like to see the encoding
defined now, so that where only simple changes are required, they
can be done quickly when desired.