The VMS distribution contains the VMS specific files:

vmsmake.com
vms.sl
vms_shell.com
keptjed.com
jed_mail.com
init_jed.com

Overview:

   All relevant files must be placed in a directory and the logical name
   JED_LIBRARY must be defined to point to this directory.  JED will load 
   files from this directory as needed.   For fast loading of the library
   files, it is recommended that they be precompiled (see below).
   
   JED may be run two ways: as a kepteditor in a subprocess and as a 
   standalone executable.  If you do alot of editing, I recommend running
   JED as a kept editor.  The file init_jed.com determines how this is 
   done.  See below.
   
Building and installing JED   
To build JED and install JED on VMS, do the following:

0. Decide where you want the JED library files to reside.  Define the 
   logical name `JED_LIBRARY' to point to this directory.  This logical name
   must be placed in the job table or the system table.  The system table is
   appropriate for most systems.  Examples:
   
     define/system JED_LIBRARY dev$disk:[appl.jed]
     define/job JED_LIBRARY dev$user:[moi.jed]
     
   It is best to put the definition in the appropriate startup file
   (systartup.com, sylogin.com, login.com).
     
1. Build the jed.exe executable file: 
   This may require editing the file vmsmake.com if you wish to use 
   gcc or do not want floating point installed.  Directions are included
   in vmsmake.com.
   
   Currently the file is structured such that typing `@vmsmake' at the VMS
   DCL prompt will make jed.exe for systems which have DEC's VMS C compiler.
   For systems that use GCC, `@vmsmake gcc' might also work.  That is:
   
     $ @vmsmake          ! VMS CC
     $ @vmsmake gcc      ! GNU GCC

2. Make a directory where the *.sl files are to be kept--- make sure it is
   world readable and copy the *.sl, *.hlp, *.com, *.info, jed.rc, and
   jed.exe files there, e.g.,

     $ create/dir/prot=(w:re) dev$disk:[appl.jedlib]
     $ copy/prot=(w:re) *.sl, *.hlp, jed.exe, *.info, *.%in, *.com, jed.rc -
        dev$disk:[appl.jed]

   The vmsmake.com file may be used to facilitate this task.  Try:
   
     $ @vmsmake.com install
      
4. Put one of the following in either your sylogin.com for all users
   or in login.com.  Note that JED_LIBRARY must be defined!

     $ @JED_LIBRARY:init_jed.com  0 0     ! no kept editor/no mail
     $ @JED_LIBRARY:init_jed.com  0 1     ! no kept editor/ use for mail
     $ @JED_LIBRARY:init_jed.com  1 0     ! kept editor/ no mail (most systems)
     $ @JED_LIBRARY:init_jed.com  1 1     ! kept editor/use for mail
     
   The first flag indicates whether jed should be installed as a standalone
   executable or as a kept editor.  Use 1 for kepteditor or 0 for standalone.
   The second flag indicates whether or not mail$edit logical should be 
   defined to point to jed.  If it is set to 1, vms mail will call jed to
   edit the mail message.  If JED is run as a kept editor, mail will simply
   attach to JED for editing.   Most systems will probably use the 3rd
   choice above.    
     
5. The file jed.rc contains the default keysettings for most users.  On VMS
   this means users will get both edt and emacs keybindings.  It is not
   necessary for every user to have a copy of this file.  JED will search
   for jed.rc in sys$login first and if not found, it will load jed.rc from
   jed_library.

6. It may be necessary to edit site.sl if you have an info directory where
   info files are kept.  If you do not understand this statement, then you
   do not have info.
   
7. Optional but highly recommended.  Byte compile the S-Lang files.  This
   is done by running JED as:
     
         $ jed -batch -n -l bytecomp
	 
   This creates pre-parsed *.slc files that load quicker than *.sl files.
   
8. Please email bugs, installation problems, or hints about how to better
   install JED to `davis@amy.tch.harvard.edu'.
