Attributes

  Global attributes are settings that apply in all buffers and can be saved
  in a section file or as EVE-generated code in a command file, so you can
  keep your settings for future editing sessions:

     SET BACKUP CONTROL STRING         SET [NO]FILE BACKUP
     SET BOX [NO]PAD                   SET FIND CASE [NO]EXACT
     SET BOX [NO]SELECT                SET [NO]PENDING DELETE
     SET [NO]CLIPBOARD                 SET [NO]SECTION FILE PROMPTING
     SET CURSOR BOUND or FREE          SET SCROLL ON, OFF, JUMP, or SMOOTH
     SET [NO]DEFAULT COMMAND FILE      SET TABS INSERT, MOVEMENT, or SPACES
     SET [NO]DEFAULT SECTION FILE      SET TABS [IN]VISIBLE
     SET [NO]EXIT ATTRIBUTE CHECK

  Other global settings are not saved, such as scroll margins or type of
  wildcards. Buffer settings, such as margins and tab stops, are not saved.

  Attributes and Section Files

     o  A section file is in binary form so it is loaded quickly at startup,
        but it cannot be printed or edited. In effect, the section file is
        your own, customized version of EVE.

     o  To create a section file, use SAVE ATTRIBUTES or SAVE EXTENDED EVE.
        A section file saves the following:

           *  Compiled procedures
           *  Global attributes  (see list above)
           *  Key definitions, including learn sequences
           *  Menu definitions for the DECwindows interface

     o  If you prefer to save in a section file, use the following commands,
        so that when you save attributes, EVE creates a new version of your
        default section file without prompting for the file name. This also
        makes attribute saving faster because there are fewer prompts.

           Command: SET NOSECTION FILE PROMPTING
           Command: SET DEFAULT SECTION FILE mysection.tpu$section
           Command: SAVE ATTRIBUTES

     o  For more information about creating and using a section file, see
        help on Section Files.

  Attributes and Command Files

     o  A command file contains TPU procedures and statements which are
        compiled and executed at startup---in effect, a series of TPU
        programs for extending EVE. A command file may be slower at startup
        than a section file, but it takes up less disk space and it can be
        edited and printed.

     o  When you use SAVE ATTRIBUTES, you can have EVE create or update a
        command file. EVE then generates a specially marked block of TPU
        statements for---

           *  Global attributes (see list above)
           *  Menu definitions for the DECwindows interface

        Thus, if you created a command file containing TPU procedures and
        key definitions of your own, you can have EVE add the block of
        statements to this command file. If there is already an attribute
        block in the command file, EVE replaces it with the new block.

     o  If you prefer to save in a command file, use the following commands,
        so that when you save attributes, EVE prompts for a command file and
        shows the name of your default command file (TPU$COMMAND.TPU) in the
        prompt line. This also makes attribute saving faster because there
        are fewer prompts.

           Command: SET NOSECTION FILE PROMPTING
           Command: SET NODEFAULT SECTION FILE
           Command: SET DEFAULT COMMAND FILE tpu$command.tpu
           Command: SAVE ATTRIBUTES

     o  For more information about using a command file, including a sample
        file, see help on Command Files.

  Attributes and Initialization Files

     o  An initialization file (typically named EVE$INIT.EVE) contains
        commands you want executed at startup. This is particularly useful
        to set margins, tab stops, and other attributes that are applied to
        the $DEFAULTS$ buffer. For example, if you prefer a right margin of
        70, put SET RIGHT MARGIN 70 in your initialization file. See help on
        Defaults.

     o  At startup, an initialization file is slower than a section file or
        command file, depending on how many commands are to be executed. For
        example, if you have several key definitions, you should save them
        in a section file.

     o  For more information about using initialization files, including a
        sample file, see help on Initialization Files.

  Attribute Checking and Exiting

     o  On exiting or quitting, if you changed attributes and have not
        already saved them, EVE asks you whether to save your changes. If
        you respond Yes, EVE does a SAVE ATTRIBUTES.

     o  To simplify or speed up exiting and quitting, you can use (and save)
        SET NOEXIT ATTRIBUTE CHECK. This is also useful if you frequently
        change global settings but do not want to save the changes. However,
        SET NOEXIT ATTRIBUTE CHECK does not apply to the current editing
        session, but only to subsequent sessions in which you use the
        section file or command file in which you saved the setting.

  Related topics:

     Command Files     Defaults            Initialization Files
     Section Files     SAVE ATTRIBUTES     SAVE SYSTEM ATTRIBUTES