Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 beta 3/9/83; site aquila.UUCP
Path: utzoo!dciem!aquila!chris
From: chris@aquila.UUCP (chris)
Newsgroups: net.micro.pc,net.unix
Subject: Re: PC/AT Function Keys under Xenix
Message-ID: <75@aquila.UUCP>
Date: Fri, 11-Apr-86 16:08:20 EST
Article-I.D.: aquila.75
Posted: Fri Apr 11 16:08:20 1986
Date-Received: Mon, 14-Apr-86 12:47:10 EST
References: <400@gargoyle.UUCP>
Reply-To: chris@aquila.UUCP ()
Distribution: net
Lines: 24
Xref: dciem net.micro.pc:7387 net.unix:7369
Summary: 


Using IBM (Microsoft) XENIX 1.00, you have to program the device driver to
tell it what to deliver when a function key is typed.  To program the
function keys, see console(M) in the manuals. I placed an initialization
string (is=) into the termcap for ansi which sets the function keys up to
generate ANSI sequences.

Actually, this is overkill, because it only needs to be done once after the
machine is booted; you could place the initialization elsewhere and cat it
to the terminal when you re-boot. This saves mucking about in /etc/termcap.

As I recall, sending the terminal
	ESC Q n "code sequence for Function key n"
will program key n. Note that n ranges from 0 to 9, even though the
keys are labelled F1-F10. The double quotes can be changed to something
NOT in the code sequence if you wanted quotes in there. Be sure what
goes in the quotes is what you want your program to see -- that is,
if you use termcap, have k0 thru k9 expect these sequences.

I agree that the manuals are hard to read -- this has already been discussed.
-- 

	Chris Retterath, Consensys Corporation, Toronto, Canada.
	{allegra|decvax|duke|ihnp4|linus|watmath}!utzoo!dciem!aquila!chris