From: Mark Wooding Date: Mon, 17 Jun 2024 10:21:48 +0000 (+0100) Subject: Fix a number of random typos in source commentary and documentation. X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~mdw/git/runlisp/commitdiff_plain/3b27cf53da4dd3258fdc47b74633ae928428c879?ds=sidebyside Fix a number of random typos in source commentary and documentation. No code changes at all. --- diff --git a/README.org b/README.org index c4aad72..482791d 100644 --- 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*~, - 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. @@ -177,7 +177,7 @@ prints values as if by ~prin1~. For example, : $ 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 @@ -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 - 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. @@ -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. -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 @@ -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 -you set that. +you set that variable. ** 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 -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 @@ -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. + +* 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 diff --git a/doc/README.pdf b/doc/README.pdf index 38f74ff..b7c456c 100644 Binary files a/doc/README.pdf and b/doc/README.pdf differ diff --git a/dump-runlisp-image.c b/dump-runlisp-image.c index 72ce97d..dfae56f 100644 --- a/dump-runlisp-image.c +++ b/dump-runlisp-image.c @@ -447,7 +447,7 @@ static void hash_input(struct linebuf *buf, size_t n, struct sha256_state *h) /* Collect output lines from JOB's process and write them to the log. * * Read data from BUF's file descriptor. Output complete (or overlong) lines - * usng `write_line'. On end-of-file, output any final incomplete line in + * using `write_line'. On end-of-file, output any final incomplete line in * the same way, close the descriptor, and set it to -1. * * As a rather unpleasant quirk, if the hash-state pointer H is not null, @@ -1466,7 +1466,7 @@ int main(int argc, char *argv[]) #undef FLAGOPT - /* CHeck that everything worked. */ + /* Check that everything worked. */ optind++; if ((flags&AF_ALL) ? optind < argc : optind >= argc) flags |= AF_BOGUS; if (flags&AF_BOGUS) { usage(stderr); exit(127); } diff --git a/lib.c b/lib.c index d369e7d..99cad5d 100644 --- a/lib.c +++ b/lib.c @@ -1638,7 +1638,7 @@ static const char *subst(const char *p, const char *l, /* If there's an alternative, then we need to process (or maybe * skip) it. Otherwise, we should complain if there was no - * veriable, and we're not skipping. + * variable, and we're not skipping. */ if (p < l && *p == '?') p = subst(p + 1, l, sb, file, line, subqfilt, diff --git a/lib.h b/lib.h index 0e285a4..cba8965 100644 --- a/lib.h +++ b/lib.h @@ -400,8 +400,8 @@ struct treap_node { /* We can't allocate nodes ourselves, because only the caller knows how. * Instead, insertion is split into two operations: `treap_probe' looks to * see whether a matching node is already in the treap, and returns it if so; - * otherwise, it flls in this `treap_path' structure, which is passed back to - * `treap_insert' to help it add the fresh node into the treap. (See the + * otherwise, it fills in this `treap_path' structure, which is passed back + * to `treap_insert' to help it add the fresh node into the treap. (See the * commentary in `treap_probe' and `treap_insert' for the details.) */ #define TREAP_PATHMAX 64 diff --git a/runlisp.conf.5.in b/runlisp.conf.5.in index d94fdf5..9e67af4 100644 --- a/runlisp.conf.5.in +++ b/runlisp.conf.5.in @@ -509,7 +509,7 @@ but this is not recommended. . .SS "Predefined variables in @BUILTIN" The -.B @BULITIN +.B @BUILTIN section has no parents. You should not override its settings in configuration files. It holds a number of variables set by the