README.org: Use correct `\nbsp{}' to prevent line breaks at spaces.

Writing the TeX-like `~' just typesets a tilde.

diff --git a/README.org b/README.org
index 4a4ee011c67ec96fe33167c6a6050a298eebf524..973ce36a0745056035197201da10c53682c2f4ad 100644 (file)
--- a/README.org
+++ b/README.org
@@ -264,10 +264,10 @@ as possible.  An awkward Lisp will of course cause trouble, but
 ~runlisp~ itself is easy.
 
 As a simple example, let's add support for the 32-bit version of
 ~runlisp~ itself is easy.
 
 As a simple example, let's add support for the 32-bit version of

-Clozure~CL.  The source code for Clozure~CL easily builds both 32- and
-64-bit binaries in either 32- or 64-bit userlands, and one might
-reasonably want to use the 32-bit CCL for some reason.  The following
-configuration stanza is sufficient
+Clozure\nbsp{}CL.  The source code for Clozure\nbsp{}CL easily builds
+both 32- and 64-bit binaries in either 32- or 64-bit userlands, and one
+might reasonably want to use the 32-bit CCL for some reason.  The
+following configuration stanza is sufficient

 
 : [ccl32]
 : @PARENTS = ccl
 
 : [ccl32]
 : @PARENTS = ccl


@@ -345,8 +345,9 @@ Let's take this in slightly larger pieces.
     we add the tokens ~--core "${image-path}" --eval "${image-restore}"~
     to the SBCL command line; otherwise, we add ~--eval
     "${run-script-prelude}"~.  The ~@IMAGE~ setting is defined by
     we add the tokens ~--core "${image-path}" --eval "${image-restore}"~
     to the SBCL command line; otherwise, we add ~--eval
     "${run-script-prelude}"~.  The ~@IMAGE~ setting is defined by

-    ~runlisp~ only if (a)~a custom image was found in the correct place,
-    and (b)~use of custom images isn't disabled on its command line.
+    ~runlisp~ only if (a)\nbsp{}a custom image was found in the correct
+    place, and (b)\nbsp{}use of custom images isn't disabled on its
+    command line.

 
     The ~${image-path}~ token expands to the full pathname to the custom
     image file; ~image-restore~ is a predefined Lisp expression to be
 
     The ~${image-path}~ token expands to the full pathname to the custom
     image file; ~image-restore~ is a predefined Lisp expression to be


@@ -410,8 +411,8 @@ I timed how long it took to run on all of ~runlisp~'s supported Lisp
 implementations, and compared them to how long ~cl-launch~ took: the
 results are shown in table [[tab:runlisp-vanilla]].  ~runlisp~ is /at least/
 two and half times faster at running this script than ~cl-launch~ on all
 implementations, and compared them to how long ~cl-launch~ took: the
 results are shown in table [[tab:runlisp-vanilla]].  ~runlisp~ is /at least/
 two and half times faster at running this script than ~cl-launch~ on all

-implementations except Clozure CL[fn:slow-ccl], and approaching four and
-a half times faster on SBCL.
+implementations except Clozure\nbsp{}CL[fn:slow-ccl], and approaching
+four and a half times faster on SBCL.

 
 #+CAPTION: ~cl-launch~ vs ~runlisp~ (with vanilla images)
 #+NAME: tab:runlisp-vanilla
 
 #+CAPTION: ~cl-launch~ vs ~runlisp~ (with vanilla images)
 #+NAME: tab:runlisp-vanilla


@@ -494,8 +495,8 @@ XPS13 laptop running Debian `buster'.  The tools used to make the
 measurements are included in the source distribution, in the ~bench/~
 subdirectory.)
 
 measurements are included in the source distribution, in the ~bench/~
 subdirectory.)
 

-[fn:slow-ccl] I don't know why Clozure CL shows such a small difference
-here.
+[fn:slow-ccl] I don't know why Clozure\nbsp{}CL shows such a small
+difference here.

 
 ** It's inconvenient
 
 
 ** It's inconvenient