The disp.map file maps display names onto known terminal types.
Obviously this will need changing for your own site.

In mach.c, the routine machDetails() defaults all displays beginning
with "xt" to NCD X terminals.  We did this because UKC has zillions
of them and so this is a simple way of keeping the disp.map file
below 10MB :-) change, remove etc.  at your leisure.

paths.h indicates where the all the *.map and program files live; the
non-debugged installation directory should be the same as the AUX
variable in Makefile.


New version of 'Xops'
~~~~~~~~~~~~~~~~~~~~~

It's now called xterm-wrapper and lives in /usr/research/lib/xterm-wrapper.

xwrap,xops,xorigami,xfe are symlinks to the first program
/usr/l/lib/xterm-wrapper/xterm-wrapper.

Example, by way of explanation.

When xfoo is called, the following happens:

% xfoo bar.occ

  xfoo is invoked which is a symlink to
  /usr/research/lib/xterm-wrapper/xterm-wrapper. 

  xterm-wrapper notices the name and does the usual stuff, handling
  the -b, -h, -v, -m machine, -a options.  It reads the display and
  machine database as normal to determine the keyboard type to use.

  IF UKC_FUDGE_KEYMAPS is being done, it then trys to run a script
  /usr/research/lib/xterm-wrapper/fix-<termtype> if it exists and
  is executable.  This can be used to fix broken X terminals.

  It then exec()s xterm with the following arguments:

  xterm -title Xfoo(termtype) -name Xwrapper(termtype)
        -e /usr/research/lib/xterm-wrapper/app-wrapper termtype foo bar.occ

  xterm (/usr/local/X11/xterm) is invoked.
  It opens a window and executes the command given:

  /usr/research/lib/xterm-wrapper/app-wrapper termtype foo bar.occ

  app-wrapper uses the termtype name to set TERM=termtype.  It then
  exec()s the remaining arguments:

  foo bar.occ

Special magic for 'xwrap'.  Just run the program given in the window.

UKC NOTES:

Fe works like above BUT the /usr/l/bin/fe program is a wrapper for
the real one, setting and resetting the keypad into application mode.
Xwrapper doesn't care about this though.

For MEIKO programs:

Special magic for 'xops'.  Ignore 'ops' or 'trun' as the first
command and in the former continue with 'ops', in the latter, run
'trun' instead.  Give a warning in both cases.  Also if the first
argument doesn't look like an argument or number (argument to 'ops')
then assume it's a script and tell the user to run 'xwrap script'
instead.

Special magic for 'trun'.  Warn if the first argument is 'trun' but
ignore it.

