Fix a number of random typos in source commentary and documentation.

[runlisp] / README.org

diff --git a/README.org b/README.org
index c4aad72df21284b803a9a8c71418574c925ac8f5..482791d1b94bf072515f4b0b28b29bec0412978b 100644 (file)
--- a/README.org
+++ b/README.org
@@ -122,7 +122,7 @@ For example:
 
   + The prevailing Unix standard input, output, and error files are
     available through the Lisp ~*standard-input*~, ~*standard-output*~,
 
   + The prevailing Unix standard input, output, and error files are
     available through the Lisp ~*standard-input*~, ~*standard-output*~,

-    and ~*error-ouptut*~ streams, respectively.  (This is, alas, not a
+    and ~*error-output*~ streams, respectively.  (This is, alas, not a

     foregone conclusion.)
 
   + The keyword ~:runlisp-script~ is added to the ~*features*~ list.
     foregone conclusion.)
 
   + The keyword ~:runlisp-script~ is added to the ~*features*~ list.


@@ -177,7 +177,7 @@ prints values as if by ~prin1~.  For example,
 
 : $ runlisp -p '"Hello, world!"'
 : Hello, world!
 
 : $ runlisp -p '"Hello, world!"'
 : Hello, world!

-: runlisp -d '"Hello, world!"'
+: $ runlisp -d '"Hello, world!"'

 : "Hello, world!"
 
 In addition to evaluating forms with ~-e~, and printing their values
 : "Hello, world!"
 
 In addition to evaluating forms with ~-e~, and printing their values


@@ -226,7 +226,7 @@ The ~runlisp~ program looks for configuration in a number of places.
     All of the files in this directory named ~SOMETHING.conf~ are read,
     in increasing lexicographical order by name.  The package comes with
     a file ~0base.conf~ intended to be read first, so that it can be
     All of the files in this directory named ~SOMETHING.conf~ are read,
     in increasing lexicographical order by name.  The package comes with
     a file ~0base.conf~ intended to be read first, so that it can be

-    overridden if necessar.  This sets up basic definitions, and defines
+    overridden if necessary.  This sets up basic definitions, and defines

     the necessary runes for those Lisp implementations which are
     supported `out of the box'.  New Lisp packages might come with
     additional files to drop into this directory.
     the necessary runes for those Lisp implementations which are
     supported `out of the box'.  New Lisp packages might come with
     additional files to drop into this directory.


@@ -242,7 +242,7 @@ The ~runlisp~ program looks for configuration in a number of places.
     directories to add support for privately installed Lisp systems, or
     to override settings made by earlier configuration files.
 
     directories to add support for privately installed Lisp systems, or
     to override settings made by earlier configuration files.
 

-But configuration files generally look like =.ini=-style files.  A line
+Configuration files generally look like =.ini=-style files.  A line

 beginning with a semicolon ~;~ is a comment and is ignored.  Most lines
 are assignments, which look like
 #+BEGIN_QUOTE
 beginning with a semicolon ~;~ is a comment and is ignored.  Most lines
 are assignments, which look like
 #+BEGIN_QUOTE


@@ -260,7 +260,7 @@ Configuration options can also be set on the command line, though the
 effects are subtly different.  Again, see the manual pages for details.
 
 [fn:xdg-config] More properly, in ~$XDG_CONFIG_HOME/runlisp.conf~, if
 effects are subtly different.  Again, see the manual pages for details.
 
 [fn:xdg-config] More properly, in ~$XDG_CONFIG_HOME/runlisp.conf~, if

-you set that.
+you set that variable.

 
 
 ** Deciding which Lisp implementation to use
 
 
 ** Deciding which Lisp implementation to use


@@ -574,7 +574,7 @@ impossible to access.
 : NIL
 
 As another example, Armed Bear Common Lisp doesn't seem to believe in
 : NIL
 
 As another example, Armed Bear Common Lisp doesn't seem to believe in

-the stderr stream: when it starts up, ~*error-ouptut*~ is bound to the
+the stderr stream: when it starts up, ~*error-output*~ is bound to the

 standard output, just like ~*standard-output*~.  Also, ~cl-launch~
 loading ASDF causes a huge number of ~style-warning~ messages to be
 written to stdout, making ABCL pretty much useless for writing filter
 standard output, just like ~*standard-output*~.  Also, ~cl-launch~
 loading ASDF causes a huge number of ~style-warning~ messages to be
 written to stdout, making ABCL pretty much useless for writing filter


@@ -625,3 +625,9 @@ 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.
 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.

+
+* COMMENT Emacs cruft
+
+# LocalWords: abcl Almquist argv ATTR Attr BST clisp CLisp's Clozure CMU ecl
+# LocalWords: env fn ini interp launchrc lua nbsp noinform precompiled prin
+# LocalWords: princ sb SBCL's sed SYSCONFDIR sysinit TBLFM tbp tikz xdg XPS