Installing JED

Building jed from its sources requires the use of a C compiler that understands function prototypes. jed has been successfully built with cc on the ULTRIX, VMS, and IRIX operating systems. In addition, it has been created using gcc under SunOS and Borland's BCC 3.0 for the PC.

Detailed installation instructions are in separate, operating system dependent files. They are:

       UNIX:   install.unx
        VMS:   install.vms
      IBM-PC:   install.pc

When jed starts up, it will first try to load a site initialization file called site.sl. Site specific commands are placed here. Most likely, site.sl will define some functions, default hooks, etc...What goes in it is left to the discretion of the user or system manager. See the file site.sl for examples.

When loading site.sl as well as other S-Lang files (the user's personal initialization file, .jedrc or jed.rc, is a special case, see below), jed searches all directories specified by the environment variable JED_LIBRARY, and if the file is not found, jed will look for it in the default directory. The environment variable JED_LIBRARY is a comma separated list of directories. Here are some examples of setting this variable for different systems:

      VMS:    define/job JED_LIBRARY  dev$lib:[jedfiles]
      UNIX:   setenv JED_LIBRARY '/usr/local/lib/jed,~/jed'
      IBMPC:  set JED_LIBRARY = c:\editors\jed\lib

You will probably want to put define JED_LIBRARY in your login startup file, e.g., autoexec.bat, login.com, or .cshrc.

jed versions 0.92 and later allow the value of JED_LIBRARY to be specified at compile time an it may only be necessary to define JED_LIBRARY as an environment variable to override its pre–compiled value.