Section Files

  A section file is a binary file to save key definitions and other
  customizations---effectively, your own customized version of EVE. Default
  file type is .TPU$SECTION.

  Steps:

  1.  Compile the TPU procedures you have written to extend EVE. Use EXTEND
      commands during the editing session, or put the procedures in a
      command file executed when you invoke EVE.

  2.  Define the keys you want by using DEFINE KEY, LEARN, SET FUNCTION
      KEYS, SET GOLD KEY, and SET KEYPAD commands.

  3.  On DECwindows, you can add or delete menu items for the DECwindows
      interface by using DEFINE MENU and UNDEFINE MENU, or by choosing
      Extend Menu from the Customize menu.

  4.  Set the global attributes you want saved in the section file, such as
      bound or free cursor, tab visibility, and so on. See help on
      Attributes.

  5.  To create a section file, use SAVE EXTENDED EVE. For example, the
      following command creates a section file named MYSEC.TPU$SECTION in
      your current, default directory. On VMS, file names are not case-
      sensitive. Also, on ULTRIX, existing section files are copied to a
      backup file before being overwritten. For help on customizing the
      backup file spec, see help on SET BACKUP CONTROL STRING.

         Command: SAVE EXTENDED EVE mysec

  Usage notes:

  o  If you used SET DEFAULT SECTION FILE, then you need not specify a
     section file on the command line---SAVE EXTENDED EVE or SAVE ATTRIBUTES
     saves in your default section file.

  o  To use your section file instead of the standard EVE section file,
     invoke TPU with the /SECTION= qualifier and specify the section file.
     For example, the following DCL command uses a section file called
     MYSEC.TPU$SECTION in your SYS$LOGIN directory:

        $ EDIT/TPU /SECTION=SYS$LOGIN:mysec

  o  Alternatively, define the TPU$SECTION logical name at the system level
     to specify your section file, particularly if there is a section file
     you want to use for all or most editing sessions.

  o  In specifying the section file to be used, include its device (disk)
     and directory. Otherwise, TPU assumes the section file is in SYS$SHARE.
     For more information, see DCL help on EDIT/TPU/SECTION or see the EVE
     Reference Manual.

  o  You use one section file at a time. A section file is cumulative,
     saving the current key definitions, menu definitions, global
     attributes, and compiled procedures---and any already saved in the
     section file you are using.

  o  Margins, tab stops, and other buffer settings are NOT saved in a
     section file. To use the same buffer settings for all or most sessions,
     put the relevant commands in an initialization file (typically named
     EVE$INIT.EVE) and use that file when you invoke EVE. For example, if
     you prefer a right margin of 70, put SET RIGHT MARGIN 70 in your
     initialization file. For more information, see help on Initialization
     Files.

     +------------------------------------------------------------------+
     | A section file created on DECwindows will work on character-cell |
     | terminals and conversely.  However, some DECwindows features are |
     | are not available on character-cell terminals (such as shifted   |
     | function keys and the clipboard).  Also, a section file created  |
     | on VMS will work on ULTRIX and conversely.  However, some keys   |
     | or procedures may not work or may work differently if they use   |
     | system-specific features or differences, such as file naming.    |
     +------------------------------------------------------------------+

  Related topics:

     Attributes                 Command Files        Initialization Files
     SAVE ATTRIBUTES            SAVE EXTENDED EVE    SET BACKUP CONTROL
     SET DEFAULT SECTION FILE   SHOW FILE BACKUP