+ 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.
: $ 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
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.
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
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
: 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
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
/* 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,
#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); }
/* 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
~mdw / runlisp / commitdiff