NAME
fermitpu - EDT-style keypad, EVE editing package layered on nu/TPU.
SYNOPSIS
setup fermitpu
tpu [-options] [filename]
DESCRIPTION
Fermitpu is an editing interface layered on top of the nu/TPU product. It
provides an EDT-style keypad by default, along with full compatibility with
Digital Equipment Corporation's EVE (Extensible VAX Editor) from VMS V6.1.
nu/TPU is a programming language designed to emulate the DECTPU programming
language. It is a language specifically designed for writing editors. It
is *not*, by itself, an editing interface.
The nu/TPU product is delivered with two editing interfaces -- that is,
nu/TPU comes with two editors written in the nu/TPU programming language:
SI the Simple Interface
eve.sec
an interface compatible with EVE from VMS V5.4 at the callable EVE
procedure level
Fermitpu is a port of EVE from VMS V6.1. It is compatible at the TPU
source code level and all levels of internal EVE procedures. It uses the
EDT-style keypad by default.
Here are the commands to use in order to call the three different section
files available with fermitpu (and nu_tpu):
% setup fermitpu
% tpu file # uses default FERMITPU section file
% eve file # uses default eve.sec section file
% tpu -section=si.sec # uses default si.sec section file
The best documentation on EVE and tpu programming is the EVE source code
itself, available in the directory ${FERMITPU_DIR}/eve-source. The
build.tpu file, in particular, is very useful in understanding the details
of putting together your own editing interface.
NOTE: If you already have a TPU_SECTION_FILE environmental variable set
when you setup fermitpu, it will NOT be changed! The EVE/TPU help library
environmental variables *will* be set so that they correspond to the fer-
mitpu help libraries (which is handy if you've built your own section file
on top of fermitpu), but your editing environment will NOT be changed. If
you want to use the fermitpu section file, you must make sure that you do
not have TPU_SECTION_FILE set before you setup fermitpu.
- create a file master.fil (in the same directory) that contains a list of
the files used in building the new section file
- create a version.dat file containing some information to help you keep
track of your own versioning
- build the section file on top of fermitpu using the command:
tpu \
-nodisplay \
-section=${FERMITPU_DIR}/bin/fermitpu.sec \
-output=my-tpu \
-command-${FERMITPU_DIR}/eve-source/build.tpu \
my-tpu
This will create a file my-tpu.sec which you may then use as your section file.
Note, there are other methods for building a private section file, those
methods are documented elsewhere. We recommend the above version for
reproducibility.
NOTE, tpu v5_0 (at least) does NOT produce good code when compiling on
OSF1. tpu v5_0a (and later) fixes this problem. If you are using OSF1
platforms, make sure that you have tpu v5_0a (at least) installed.
HOW TO USE YOUR OWN SECTION FILE
Use your own section file via the environmental name TPU_SECTION_FILE.
Note, if you ALWAYS want to use your own section file, then you do not need
to set up fermitpu (however, you may wish to in order to get the more
extensive VMS V6.1 online help libraries). You only need to set the
environmental variable to point to the correct file.
# setenv TPU_SECTION_FILE /path/to/my-tpu.sec
# setup tpu ! or setup fermitpu for more complete online help
# tpu xyzzy
or
# tpu -section=/path/to/my-tpu.sec xyzzy
If you build a private section file using the SI or older EVE interfaces,
then you should setup tpu so that your online help is compatible with your
section file.
DISCLAIMERS
See the file $FERMITPU_DIR/README for a whole slew of things, if you're
really interested.