Re: [Ilisp-help] Garbled documentation

   From: Edi Weitz <[email protected]>
   Date: Mon, 08 Dec 2003 00:12:39 +0100

   On Sun, 7 Dec 2003 17:56:44 -0500, Bob Rogers <[email protected]> wrote:

   > For the time being, it should work to delete ilisp-all.elc, and then
   > do "make compile" again. "(require 'ilisp)" will then load the
   > individual .elc files.

   Yes, I can confirm that this resolves the problem. Thanks for the
   quick fix.

No problem; it's always nice when there *is* a quick fix.  ;-}

   > I would argue for dropping ilisp-all.elc altogether, rather than
   > trying to make it work well both ways.  (FWIW, I don't use
   > ilisp-all.elc on my ancient 300MHz system, and I can't say I notice
   > the difference.)

   I never thought about it but now that I've removed ilisp-all.elc I
   have to say that I also don't notice a difference.

   Thanks again,
   Edi.

Since you and Bill Clementson agree, and I hear no dissenting voices, I
have taken all mention of the "loadfile" target out of the documentation
(which amounted to two versions of the same short paragraph), flushed
the "load" from ilisp.el, and fixed the Makefile so that "make loadfile"
generates a "no longer supported" message.

   I also took out the 'CONTRIBUTORS' section from ilisp.el, adding a
few overlooked names to the ACKNOWLEDGMENTS file, and the 'KNOWN BUGS'
section, since these seemed to be only of historical interest.  The
deleted text is reproduced below for reference.  If anybody thinks these
should be kept, then you are welcome to add it back, though I would
argue that ilisp.el is not the best place for them.

					-- Bob Rogers
					   http://rgrjr.dyndns.org/

------------------------------------------------------------------------
;;;%%KNOWN BUGS
;;; 
;;; If you type multiple things to the top level before you get a
;;; prompt, the LISP may be running with the status light indicating
;;; ready.  This is because I have no way to distinguish between input
;;; to a program and that to the top level.
;;;
;;; When running a lisp on Ultrix, you need to set ilisp-program to
;;; "/bin/sh -c your/path/your-lisp-image".
;;; 
;;; If you get lisp output breaking up in weird places it almost
;;; certainly means that comint-prompt-regexp is not precise enough.
;;;
;;; I would like to eat Lucid's return from break in the process
;;; filter, but I can't tell how many newlines to eat after.


;;;%%CONTRIBUTORS

;; Recent contributors include (in alphabetical order):

;; Marco Antoniotti, Robert P. Goldman, Larry Hunter, Eyvind Ness, 
;; Ivan Vazquez, Fred White


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/