[comp.windows.x] vt100 PF keys in an xterm

robc@uswat.uswest.com (Rob Cuthbertson) (02/11/90)

We have recently moved an application from SunView to X, and have ironed out
all but one glitch.  One of our tools needs a vt100 emulator as its interface,
and worked fine under SunView using vt100tool.  It now works almost perfectly
under X using a normal xterm, but we seem to have lost keys PF1 - PF4
Using vt100tool, these were bound to the Sun3 keypad keys R1 - R4, but I
can't seem to find the bindings for xterm.

Details, Details:
	Sun3/50 and 3/110 workstations as display units, Sun 4/280 as (cpu) server
	SunOS 4.0.3 all around
	X11R4 but have the same problem under R3
	twm (if that matters)

Please e-mail replies.  I will e-mail summaries if requested.

--Rob Cuthbertson, US WEST Advanced Technologies
  robc@uswest.COM (uswat.uswest.com if your sendmail needs 3 fields)
  ..!{ncar, uunet, ucbvax}!boulder!uswat!robc

robc@uswat.uswest.com (Rob Cuthbertson) (02/13/90)

Many thanks to those (MANY) people who replied, I have been given the fix 
using the VT100 widget, which consists of adding the following to .Xdefaults:

+----------------------------
# make the keypad R1-R4 work like vt100 PF1-PF4

xterm*VT100.Translations: #override <Key>R1: string("^[OP") \n \
	<Key>R2: string("^[OQ") \n \
	<Key>R3: string("^[OR") \n \
	<Key>R4: string("^[OS") \n 
+----------------------------

Of course, the ^[ should be a real escape, not ^ followed by [

I am posting this for two reasons, first in two days (weekend, no less) I
got about a dozen requests for summaries, and second I am being inundated 
with replies, most of which are similar to this technique.

Many thanks!
--Rob Cuthbertson, US WEST Advanced Technologies
robc@uswat.uswest.COM