UNIX installation specific functions.  Please read this file.

0. Building and installing JED requires that you also have the S-Lang library
   to link to (cc *.c -lslang).  Build it first.  It should be in ../slang.
   You may have to get this library if you do not already have it or your
   version is too old.  Get it from space.mit.edu in pub/davis/slang.

1. Pick some place for JED.
   JED is distributed in a TREE structure:

     $JED_ROOT/
     $JED_ROOT/src
     $JED_ROOT/info
     $JED_ROOT/doc
     $JED_ROOT/lib
     $JED_ROOT/bin

   Here JED_ROOT can be anything (e.g., /usr/local/jed).  It must be
   specified in the makefile of the src subdirectory.  It is important
   that the subdirectories under $JED_ROOT remain intact.  An
   environment variable called `JED_ROOT' can also be created to over
   ride the value compiled with the executable.

3. Build JED.

   Do the following:
   
      ./configure
      
   This will create src/Makefile.  You may need to edit it to set JED_ROOT
   appropriately.
		  
	 * note:  On Linux systems, JED may be compiled to take advantage of
	          the GPM mouse server.  See the mouse section in the
		  makefile for enabling this.

         * note:  If you are building jed on a system that uses more than
	          one architecture, before running make, define an
		  environment variable called ARCH whose value is that
		  returned by the `arch' command, e.g.,
		  
		      setenv ARCH `arch`            # csh, tcsh
		      ARCH=`arch`; export ARCH      # bash
		  
		  Alternatively, simply define this in the makefile, e.g.,
		  
		      ARCH = sun4
		      
		  Since all slang programs will use this mechanism, you are
		  encourage to add this to your shell startup file, e.g.,
		  .cshrc, .bashrc, .profile,...

   Then type `make' at the prompt.  If you have X windows and you
   would like to create 'xjed', additionally run 'make xjed'.  If all
   goes well install it with `make install'.

   JED comes with a highlighting recursive grep program called rgrep. This
   is created as part of the build process.
   
4. By default, when JED starts up, it will load some files out of
   $JED_ROOT/lib then it will look for the file .jedrc in your home directory.
   If it does not find it, it will load the default file from $JED_ROOT/lib.
   This will give you both emacs and edt emulation.  If you do not want
   that, you will need to copy $JED_ROOT/lib/jed.rc to $HOME/.jedrc and edit it.
   
   In fact, you are encouraged to copy jed.rc to $HOME/.jedrc and make your
   own personal changes there.  The jed.rc file should be regarded as a
   template for .jedrc and should not be changed.  Many Unix users do not
   want EDT editor bindings.  However, JED is shipped with the EDT bindings
   enabled.  If you do not want the EDT bindings, disable them in your .jedrc
   file.

   Site specific customization should be placed in defaults.sl. For
   example, my defaults.sl on my linux system simply loads linux.sl.
   (See linux.sl) This sets keybindings for the appropriate for
   console and sets the color to white on blue.

   See site.sl for details.  
   
5. Optional but highly recommended.  Preparse the S-Lang files.  This
   is done by running JED as:
     
         % jed -batch -n -l preparse.sl

   This creates pre-parsed *.slc files that load quicker than *.sl
   files. If this step fails to work for some reason, JED is probably
   not properly installed.  Note that the bytecodes that are stored in
   the preparsed files (*.slc) may depend upon the version of the
   slang library that was used.  This is particularly relevant if jed
   is dynamically linked to the slang library and for some reason you
   upgrade the library.  If you do this, then immediately after
   installing a new version of the slang library, run the command
   `touch *.sl' on all the .sl files in the $JED_ROOT/lib directory.
   See the release notes (changes.txt) that are distributed with the
   slang library to see if any of the byte-codes have changed.

6. Read the bit about defaults.sl in install.all for customizing your
   distribution. 
   
7. New releases will be announced to the slang mailing lists as well
   as the newsgroups comp.editors and alt.lang.s-lang.  See
   http://space.mit.edu/%7Edavis/slang.html for more information about
   the mailing lists.  Additional information may be found at
   http://www.s-lang.org.
       
8. That's it.  Enjoy.

--John
