Before reading this, read the appropriate install file for you system, e.g., install.unx. For MSDOS, WINDOWS, or OS/2, read INSTALL.pc. This file contains hints for customizing JED in such a way that it is easy to upgrade to later releases. When JED starts up, it reads the file `site.sl' which is located in the lib directory under JED_ROOT. This file contains much of the code that defines the look of the editor. For instance, it defines how the command line parameters are to be interpreted and the name of the user's personal initialization file. One could always edit site.sl and taylor it to the needs of a given system. However, one would have to do this with every upgrade. There is a better way. Immediately after loading site.sl, the editor will attemp to load a file called `defaults.sl' from JED_ROOT/lib. This file is not distributed with JED. It is up to the installer to create this file if that is the desire. An example called `linux.sl' is provided for Linux systems. Linux administrators are encouraged to pattern their defaults.sl file after linux.sl. What is this file used for? It is used to modify site.sl. Since site.sl is written in S-Lang, any of the functions defined in it can simply be redefined by creating new ones. The same is true for the variables that it defines. For example, many systems have a directory where info files are kept. Let's assume that this directory is `/usr/info'. Then one should point the `Info_Directory' variable defined by `site.sl' to this directory: % defaults.sl Info_Directory = "/usr/info"; It is probably a good idea to copy the files in JED_ROOT/info to directory where the info files are kept and edit the info DIR file appropriately. Another idea is to take advantage of the fact that JED's info reader has the ability to search along a path list. Simply edit the /usr/info/DIR file and add jed to the tree but leave JED's info files in JED_ROOT/info. Then, use something like: %defaults.sl Info_Directory = strcat ("/usr/info,", Info_Directory); Enjoy.