ilisp / INSTALLATION

Diff from to

INSTALLATION

 
 FIRST INSTALLATION STEP: UNPACKING AND COMPILING.
 
-Copy the ILISP distribution archive, e.g. ilisp-5.9.4.tar.gz, to the
+Copy the ILISP distribution archive, e.g. ilisp-x.y.z.tar.gz, to the
 location where you would like to install it. Next extract the archive (you
 may need root privileges to perform these operations):
 
-% gzip -dc ilisp-5.9.4.tar.gz | tar xf -
+% gzip -dc ilisp-x.y.z.tar.gz | tar xf -
 
 or:
 
-% unzip ilisp-5.9.4.zip
+% unzip ilisp-x.y.z.zip
 
 Some configuration needs to be done before compiling the Emacs Lisp files
 that comprise ILISP.  Start with the Makefile file, in the section after
 
 First, set the EMACS variable to be the pathname of the Emacs you will be
 using ILISP with.  This is the Emacs that will be used to compile ILISP
-with.
+with.  Be sure to check that LN and HyperSpec have appropriate values for
+your system, ESPECIALLY IF YOU ARE A WINDOWS USER.
 
 If your Emacs supports the `easymenu' package, it is possible to make ILISP
 add to Lisp mode buffers and buffers with inferior Lisp processes, or to
 Scheme mode buffers and buffers with inferior Scheme processes, an Ilisp
 menu with all available commands.  To enable this feature, set to T the
-variable ENABLE-ILISP-CL-EASY-MENU-P in `ilisp-def.el' for the Common Lisp
-dialects, and ENABLE-ILISP-SCHEME-EASY-MENU-P for Scheme dialects.  Setting
-these variables also causes the default Lisp menu to be removed before
-displaying the Ilisp one.
+variable ILISP-*ENABLE-CL-EASY-MENU-P* in `ilisp-def.el' for the Common
+Lisp dialects, and ILISP-*ENABLE-SCHEME-EASY-MENU-P* for Scheme dialects.
+Setting these variables also causes the default Lisp menu to be removed
+before displaying the Ilisp one.
 
 See the next section for additional configuration options and known
 problems for specific Lisp dialects.
 inclusion since version 5.9 of ILISP of the `hyperspec' packages, make
 access to the Franz documentation no longer necessary. So by default ILISP
 does not load the `fi:clman' module, but if you still want to use its
-commands set the ILISP-USE-FI-CLMAN-INTERFACE-P to T in `ilisp-def.el'.
+commands set the ILISP-*USE-FI-CLMAN-INTERFACE-P* to T in `ilisp-def.el'.
 
-The ILISP documentation consists of a user manual and a reference card.
-Both of them are in the `docs' directory of the distribution tree.
+The ILISP documentation consists of a user manual and a reference card (the
+latter may not be up to date).  Both of them are in the `docs' directory of
+the distribution tree.
 
-The generation of GNU Info, DVI, PostScript and HTML versions of the manual
-from the Texinfo source is controlled by the `Makefile' in the `docs'
-directory.  Run `make docs' or just `make' to generate all of the formats.
-If you are interested in only some of them then issue the appropriate
-command: `make info' for GNU Info, `make dvi' for DVI, `make ps' for
-PostScript and `make html' for HTML.  To remove the intermediate files
-produced during the generation of DVI output you can run `make tmpclean'.
+The generation of GNU Info, DVI, PostScript and HTML versions of the
+documentation from the Texinfo and TeX source is controlled by the
+`Makefile' in the `docs' directory.  Run `make docs' or `make' to generate
+all of the formats.  If you are interested in only some of them then issue
+the appropriate command: `make info' for GNU Info, `make dvi' for DVI,
+`make ps' for PostScript and `make html' for HTML.  To remove the
+intermediate files produced during the generation of DVI output you can run
+`make tmpclean'.  Note that some of the output formats may not be supported
+for certain documents.
 
-The ILISP reference card is available in DVI and PostScript formats
-together with the TeX source.  Check the comments at the beginning of the
-TeX source if you need to generate a version with a different number of
-columns.
+The ILISP reference card is available as a TeX source file.  Check the
+comments at the beginning of the file if you need to generate a version
+with a different number of columns (the default is 3).
 
 
 SECOND INSTALLATION STEP: DIALECT REQUIREMENTS.
 	of this setting.
 
 
-o Harlequin
+o Harlequin/Xanalys LispWorks
 
-	No known extra installation glitches
+        On Windows and Linux, the LispWorks executable should be resaved
+        without the GUI.  In addition, on Windows it MUST be resaved as a
+        console application to ensure correct interaction with Emacs shell
+        buffers.  Create a script (let's call it `console.lisp') including
+        the following:
+
+          (load-all-patches)
+          (save-image "lw41-console" :console t :environment nil)
+          (quit)
+
+        and run it using:
+
+          <dir>/lispworks-4100 -init <dir>/console.lisp
+
+        When the `lw41-console' image has been created, it can be used as
+        the value of the `lispworks-program' variable in ILISP.
+
+        If you are using LispWorks 4.1.19 with Emacs 20.4 or higher on
+        Windows, then you will need an additional patch
+        `emacs20-terminal-io', available from <lisp-support@xanalys.com>,
+        because Emacs has changed the coding-system used for comint
+        buffers.  The LispWorks for Windows 4.1.20 patch bundle includes
+        some more patches (LSC #7270, LSC #7727 and LSC #7291) that make it
+        work with ILISP.  For more information check the README file which
+        comes with the bundle.
 
 
 o Lucid
 
         The following lists some unusual ILISP behaviour related to CLISP.
         Some of these are of general interest, and should hopefully be
-        fixed in an upcoming ILISP distribution. Most of these points were
+        fixed in an upcomming ILISP distribution. Most of these points were
         reported by Bruno Haible.
 
         - On startup, ILISP presents a Lisp prompt and shortly afterwards
 
             (define-c-external (nobuff) void "nobuff")
             (nobuff)
+
+
+TIPS
+
+o Enlightment window manager under Gnome
+
+        If ILISP popup windows unexpectedly keep the input focus, in the
+        Enlightment Configuration Editor choose the "Beahvior" item and
+        toggle off all the "[...] get keyboard focus" items.
+
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.