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

[runlisp] / README.org

diff --git a/README.org b/README.org
index 482791d1b94bf072515f4b0b28b29bec0412978b..62f521636b5d25e35ef263cafaf60a5dab1fce29 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,
 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
 
 
 * COMMENT Emacs cruft