Initialization Files

  An initialization file contains EVE commands, typically to set margins,
  tab stops, and other buffer attributes, or to define keys that are not
  saved in a section file. Default file type is .EVE.

  Example:

     The following is a sample EVE initialization file to set margins and
     other attributes and to define some keys:

     +-----------------------------+
     | SET LEFT MARGIN 4           |   Each command must be on a separate
     | SET PARAGRAPH INDENT +3     |   line.  If a command is incomplete,
     | SET RIGHT MARGIN 72         |   EVE prompts you for any required
     | SET TABS EVERY 10           |   information before continuing to
     | SET SCROLL MARGINS 9% 9%    |   execute the initialization file.
     | SET FIND WHITESPACE         |
     | ! Key definitions           |   Comments must be on lines separate
     | SET KEYPAD EDT              |   from commands and must begin with
     | DEF KEY= F20  SHOW BUFFERS  |   an exclamation point (!).
     | DEF KEY= CTRL/P  BOX PASTE  |
     | DEF KEY= GOLD-S  BOX SELECT |
     | DEF KEY= KP7  WPS GOLD-R    |
     +-----------------------------+

  Usage notes:

  o  To use an initialization file when you invoke EVE, do any of the
     following:

     *  Create an initialization file named EVE$INIT.EVE in your current,
        default directory or your SYS$LOGIN directory. By default, EVE looks
        for this initialization file at startup (you need not use the
        /INITIALIZATION qualifier).

     *  Define the EVE$INIT logical name to specify your initialization
        file. This is useful if you want to use the same file for all or
        most editing sessions---including when you use EVE within MAIL---and
        lets you keep the file in any directory or subdirectory you like.
        This overrides the search for an EVE$INIT.EVE file. If you omit
        parts of the file specification from the logical name
        definition---for example, if you do not specify a device
        (disk)---EVE supplies them from EVE$INIT.EVE in your current,
        default directory or your SYS$LOGIN directory.

     *  Invoke EVE using the /INITIALIZATION= qualifier and specify the
        initialization file. This overrides any definition of the EVE$INIT
        logical name and overrides the search for an EVE$INIT.EVE file. If
        you omit parts of the file specification---for example, if you do
        not specify a device (disk)---EVE supplies them first from the
        logical name (if defined), and then from EVE$INIT.EVE in your
        current, default directory or your SYS$LOGIN directory. For more
        information, see DCL help on EDIT/TPU/INITIALIZATION or see the EVE
        Reference Manual.

  o  At startup, commands in an initialization file for buffer settings,
     such as margins, paragraph indent, and tab stops, apply to the MAIN (or
     first) buffer and to an EVE system buffer named $DEFAULTS$, so that
     each buffer you create has the same settings---in effect, your own,
     private defaults. For example, if you prefer a right margin of 70, put
     SET RIGHT MARGIN 70 in your initialization file. See help on Defaults.

  o  Settings and key definitions in an initialization file override those
     in a section file or command file. Typically, you use a section file to
     save key definitions and global attributes (such as if you always want
     the EDT keypad and a bound cursor), and use an initialization file for
     buffer settings, such as margins and tab stops.

  o  To execute an initialization file during a session, use the @ command
     (at sign). This is effectively the same as typing the commands the file
     contains. Commands in the initialization file for editing operations or
     buffer settings apply to the current buffer.

  o  You can also use an initialization file when you invoke EVE for batch
     editing. For example, the following command invokes EVE using an
     initialization file named BATCH.EVE:

        $ EDIT/TPU /NODISPLAY /INITIALIZATION=batch

     This batch initialization file should comprise a complete editing
     session, including EXIT or QUIT. Some EVE commands cannot be used in
     batch because they prompt for a key press or other interactive
     response.

  o  To insert text from within an initialization file, use the TPU command
     and the EVE$INSERT_TEXT procedure. This is useful to insert a device
     control string, date and time, standard heading, or some other text at
     startup. For example, the following command in an initialization file
     inserts the quoted string:

        TPU EVE$INSERT_TEXT ("Top Secret!");

  o  To repeat a command from within an initialization file without
     requiring keyboard interaction, use the REPEAT command and specify the
     command to repeat on the same line. For example, the following command
     in an initialization file repeats the MOVE BY PAGE command 5 times:

        REPEAT 5 MOVE BY PAGE

     If you do not specify the command to repeat, EVE waits for you to press
     the key to be repeated.

  Related topics:

     @     Attributes     Command Files     Defaults     Section Files