From ...
From: Erik Naggum <erik@naggum.no>
Subject: Re: ACL 4.3 For Linux license concerns
Date: 1999/01/04
Message-ID: <3124471148557109@naggum.no>#1/1
X-Deja-AN: 428749794
References: <m3empn30w1.fsf@solo.david-steuber.com> <763ve8$a01$1@newsource.ihug.co.nz> <m31zll2lfx.fsf@solo.david-steuber.com> <m2iuewo4je.fsf@sophia.axel.nom> <m3yanriaps.fsf@solo.david-steuber.com> <m2vhiuzeb4.fsf@sophia.axel.nom> <3124350472579338@naggum.no> <slrn7927gl.10i.david.lichteblau@lambda.dummy.de>
mail-copies-to: never
Organization: Naggum Software; +47 8800 8879; http://www.naggum.no
Newsgroups: comp.lang.lisp

* david.lichteblau@snafu.de (David Lichteblau)
| Is my understanding right that the Lisp Machines have various kinds of
| listeners for purposes like this?

  I believe that's part of the package.

| Or is there one which works for normal language-oriented queries as well
| as for OS-level (:ls) things?

  :LS is ordinarily a Common Lisp keyword, but when the normal Allegro CL
  top-level read-eval-print loop reads a line that starts with the value of
  TOP-LEVEL:*COMMAND-CHAR* (ordinarily #\:), it is interpreted as a
  top-level command instead of an s-expression.  however, these commands
  are _not_ "OS-level".  :ls was intended to be an abbreviation just like
  :cf for COMPILE-FILE, :cl for COMPILE-AND-LOAD, etc, intended to mean
  LOAD-SYSTEM.

#:Erik