A section file is what nu/TPU uses to define the editing functions. An
alternative concept is that a section file gives nu/TPU its personality. Thus, using
the first command file example above, a section file is created by the SAVE (
MINI.INI”) which is then loaded as the editing interface with a subsequent
execution of nu/TPU.
Section files are binary files that contain procedures, key-maps, key
definitions, and learn sequences. A nu/TPU section file can be used across multiple
hardware and operating systems supported by nu/TPU. Section files generated from
DEC TPU are not compatible with nu/TPU.
Fast execution speed is the main benefit to section files over command and
initialization files.
V5.0 Support for Prior Version Section Files
nu/TPU v5 does not work in section files created prior to v5. Version 5 is
source code compatible with earlier versions. Thus any user extensions must be
recompiled to be available in version 5. If you are planning on using one of
the window based version of nu/TPU, it is highly recommended that you add your
extensions to the si.ini section file. Although it is possible to use the
VAX/VMS examples or some derivative, vast amounts of TPU and window function calls
would be required.
Section File