Path: utzoo!attcan!uunet!convex!killer!ames!sgi!calcite!vjs
From: vjs@calcite.UUCP (Vernon Schryver)
Newsgroups: comp.unix.microport
Subject: more 3.0e term woes
Keywords: terminfo curses function keys
Message-ID: <31@calcite.UUCP>
Date: 6 Nov 88 19:56:14 GMT
Organization: Rhyolite Software, Mountain View, CA
Lines: 26

The 3.0e+DOSMerge keyboard/screen driver, the 3.0e at386 terminfo
entry, setkey(1), and keyboard(7) in the new "Runtime" manual, and I am
are confused.  None of us can agree on what the function keys should do.

  keyboard(7) is confused.  When do you get anything involving 'B' or 'b'
	from F1?  (page 9 in keyboard(7).  And so on for the rest.
  setkey(1) talks about "/etc/rc.d/keybrd.rc", which does not exist on
	my machine.
  the 3.0e at386 terminfo entry thinks F11 and F12 do something.  They don't
	on my system unless I use setkey(1) to map them.
  there is something twisted in the default mappings for {ctrl,shift}-F*.
	Some of them are dead; others produce ^[O<char>, while their
	similarly augmented neighbors produce ^[O<control char>.
  Why does shift-<Pause/Break> do the same thing as Num-Lock?  Why is
	it impossible to generate a useful result with the <Pause/Break> key?
	One would have expected the keyboard driver to generate (the
	equivalent of) a BREAK up thru the line discipline for some
	augmentation of the key.

Vernon Scrhyver
vjs@calcite.uucp   or   ...!sgi!calcite!vjs