README.org: Mention that `runlisp' can support non-free Lisps.

The old text stated rather baldly that, if you wanted to use a non-free
Lisp system, then `cl-launch' was your only option.  This was basically
true when it was written, because that version of `runlisp' had support
for the known Lisp systems baked into the code.  (Even then, I suppose
you could have maintained a fork with the additional support.)

But now, supporting new Lisp systems is just a matter of writing the
necessary configuration runes in a text file.  This is clearly possible
and practical.  It's just that I'm not interested in carrying
configuration for non-free Lisps as part of the `runlisp' distribution.

diff --git a/README.org b/README.org
index 482791d..62f5216 100644 (file)
--- a/README.org
+++ b/README.org
@@ -623,8 +623,9 @@ supports.  If you want your scripts to be able to run on other Lisps,
 then ~cl-launch~ is the way to do that.  Of course, I welcome patches to
 help ~runlisp~ support other free Lisp implementations.  ~cl-launch~
 also supports proprietary Lisps: I have very little interest in these,
-so if you want to run scripts using Allegro or LispWorks then
-~cl-launch~ is your only choice.
+so if you want to run scripts using Allegro or LispWorks then your only
+options are to maintain your own ~runlisp~ configuration for these
+systems or to use ~cl-launch~.
 
 * COMMENT Emacs cruft
 

diff --git a/doc/README.pdf b/doc/README.pdf
index b7c456c..623a598 100644 (file)
Binary files a/doc/README.pdf and b/doc/README.pdf differ