Getting Started with EVEDT, excerpted from EVEDTDOC.MEM

        1.2  GETTING STARTED

        Before you can use the EVEDT editor  you  must  first  define  it's
        location.  These  symbol  definitions  and  assignments  should  be
        included in your login command file. There are two ways  to  define
        the  editor,  either  may be used depending on your preference. The
        first method is as follows:

        ED*IT :== EDIT/TPU/SEC=EVE:EVEDT.TPU$SECTION

        Where:

        EVE is logically assigned as:

        ASSIGN DISK$2:[SHAPIRO.USERS.EVE] EVE


        The second (and recommended)  method  to  define  the  section  and
        initialization files is as follows:

        ED*IT :== EDIT/TPU

        ASSIGN DISK$2:[SHAPIRO.USERS.EVE]   EVE
             
        DEFINE/NOLOG TPU$SECTION                   EVE:EVEDT.TPU$SECTION

        In either case, you should also define the HELP logical:

        DEFINE/NOLOG EVEDT$HELP                    EVE:HELP_EVEDT.HLB

        If you want to provide  customization  for  your  editor,  you  may
        define  the  following logicals. The first may contain EVE commands
        which will be executed at  editor  startup  time.  The  second  may
        contain  TPU  commands/procedures which will be executed at startup
        time. These files are described in more detail in sections 12.2 and
        12.3

        DEFINE/NOLOG EVE$INIT     [YOUR.DIR]EVEDT$INIT.EVE 
        DEFINE/NOLOG TPU$COMMAND  [YOUR.DIR]EVEDT$COMMAND.TPU


        To envoke the editor (in either case) you would merely type:

        ED <FILENAME.EXT>

        at the VMS command line prompt to edit the file <FILENAME.EXT>


        1.3  HANDY HINTS

        Realizing that some individuals prefer the  learn-by-doing  method,
        and  only  resort to reading the instructions under threat of death
        or worse, I have compiled a list of handy hints and tips for  using
        the EVEDT editor.

       (1)  When entering EVEDT, it is a good idea to specify a filename to
            edit.  You  don't  have  to, but if you don't the text you edit
            isn't associated with a file.
       (2)  Using the BUFFER command to  get  a  new  buffer  is  sometimes
            dangerous  since  there  is no file associated with the buffer,
            instead use the GETFILE key (KP3),  this  associates  the  file
            with a buffer (and vice-versa).
       (3)  When you wish to make a different buffer  the  current  buffer,
            you  may  use  the  GETFILE key (KP3). If the buffer exists, it
            will become current, if it doesn't it will search for a file of
            the same name, and if found, make it the current buffer. If the
            file doesn't exist, it will be created and saved upon exit.
       (4)  Like  all  good  programmers,  you  should  save  your  current
            versions  at  frequent  intervals.  The GOLD O (Output to file)
            procedure is quick and easy and was intended  to  be  used  for
            this purpose.
       (5)  Select ON/OFF is a TOGGLE.
       (6)  Be careful when you are assigning a learn-ed sequence to a key.
            If the key you are assigning the sequence to is used within the
            sequence, you will put yourself into a recursive loop which may
            (probably)  do strange and wonderous things to the file you are
            editing.
       (7)  The GOLD S (SPAWN) procedure will enable you to return  to  VMS
            level  without  leaving  the edit session. This is handy if you
            wish to answer / send mail or perform other activities  at  the
            VMS  level. Don't forget to LOGOFF the spawned process when you
            have finished your activity. If you start re-editing  the  file
            which  is  being  edited in the other process, you will wind up
            with various revisions with various changes in them.
       (8)  The GOLD V (VMS Command) procedure will allow you to execute  a
            single DCL command (at a time) from within the editor.