LISP(1) LISP(1)
NAME
lisp - CMU Common Lisp programming environment
SYNOPSIS
lisp [input-files] [switch-list]
DESCRIPTION
lisp Starts up CMU Common Lisp. If switch-list is empty, then Lisp
will enter a read-eval-print loop using stdin, stdout and stderr. The
optional input-files provide operands for some switches. These
switches are defined:
-core filename
Specifies the suspended Lisp image (or `core file(1,n)') to start
up.
-lib libpath
A colon-separated list of directories to be used for the
library: search-list.
-batch Causes Lisp to run in(1,8) batch mode, where all input is directed
from standard-input. A unix return code of 0 is returned
upon encountering an EOF, while any unhandled error(8,n) condition
will cause an immediate exit(3,n,1 builtins) with a return code of 1, instead
of entering the debugger.
-quiet Causes Lisp to start up silently, disabling printing of the
herald, and causing most unnecessary noise, like GC messages,
load(7,n) messages, etc. to be suppressed.
-dynamic-space-size
Requires an argument that should be the number of megabytes
(1048576 bytes) that should be allocated to the heap. If not
specified, a platform-specific default is used. The actual
maximum allowed heap size is platform-specific. Currently,
this option is only available for the x86 and sparc plat-
forms.
-edit Causes Lisp to enter the Hemlock editor. A file(1,n) to edit may
be specified by placing the name of the file(1,n) between the pro-
gram name (usually `lisp') and the first switch.
-eval expression
Evaluates the specified Lisp expression during the start up
sequence. The value of the form will not be printed unless
it is wrapped in(1,8) a form that does output.
-init filename
Specifies the name of a file(1,n) containing user customizations
that is to be loaded each time(1,2,n) Lisp starts up (default ~/init
or ~/.cmucl-init.) The loader loads any existing compiled
binary, or the ".lisp" source if(3,n) none.
-hinit filename
Similar to -init, but specifies the name of the Hemlock init
file(1,n) (default `~/hemlock-init' or ~/.hemlock-init), which is
loaded only when Hemlock is started.
-noinit Suppresses loading of the init file(1,n), and also prevents -edit
from loading the Hemlock init file.
-nositeinit
Suppresses loading of the site-init site specific initializa-
tion file.
-load filename
Loads the specified file(1,n) into Lisp before entering Lisp's
read-eval-print loop.
-slave editor-name
Specifies that Lisp should start up as a slave Lisp and try
to connect to an editor Lisp. The name of the editor to con-
nect to must be specified. To find the editor's name, use
the Hemlock `Accept Slave Connections' command. editor-name
is of the form `machine-name:socket', where machine-name is
the internet host(1,5) name for the machine and socket(2,7,n) is the dec-
imal number of the socket(2,7,n) to connect to.
ENVIRONMENT
CMUCLLIB This variable points to the `lib/' directory holding
`lisp.core' and other files used by Lisp at run-time. This
can be overridden by using the -lib commandline option.
CMUCLCORE This variable holds the path to the `lisp.core' that that
should be used. This can be overridden by using the -core
commandline option.
CMUCL_EMPTYFILE
[SunOS only] If `df /tmp' shows `swap' as the filesystem for
the `/tmp' directory, then you have a "tmpfs" filesystem. In
this case, you must setenv CMUCL_EMPTYFILE to point into a
pathname on a non-TMPFS filesystem that can be used instead
of `/tmp/empty'.
XKEYSYMDB In order to use Motif (and the graphical debugger) with X
servers from non-OSF vendors (like Sun) you may need to set(7,n,1 builtins)
the environment variable XKEYSYMDB to point to the file(1,n)
`lib/XKeysymDB'. Otherwise, you will get many error(8,n) messages
every time(1,2,n) a new connection is opened to the CMU CL motifd.
This file(1,n) is read(2,n,1 builtins) by the X11R5 Xt in(1,8) order to augment the
keysym database with certain OSF vendor keysyms that Motif
wants to use.
CORE FILE SEARCHING
When no core file(1,n) is specified (either by the CMUCLCORE environment
variable or by the -core option), CMUCL will search in(1,8) various places
to find a possible core file.
When the environment variable CMUCLLIB is set(7,n,1 builtins) or the -lib option is
given, the lisp core file(1,n) is searched in(1,8) the places specified therein.
This is a colon-separated list of directories, just like PATH. This
list of directories is searched in(1,8) order for a file(1,n) named(5,8) `lisp.core'.
The first one found will be the core to be used.
When the CMUCLLIB is not set(7,n,1 builtins) and -lib is not given, a set(7,n,1 builtins) of default
paths is used to initialize the library: search-list, and this list is
also used to search for the core file. Let the lisp C executable be
located at `<bin>/lisp'. Then the following directories are searched
for the core file:
`<bin>'
`<bin>/../lib/cmucl/lib'
`<bin>/../lib'
`/usr/local/lib/cmucl/lib'
FILES
The following pathnames are specified relative to the directory where
CMU CL is installed, e.g. /usr/local.
doc/cmucl/*
Various postscript and text documentation files.
bin/lisp The lisp startup program. This directory should be in(1,8) PATH.
lib/cmucl/lib/lisp.core
The suspended Lisp image.
lib/cmucl/lib/site-init.lisp
Site specific initialization (see README file.)
lib/cmucl/lib/hemlock11.*,lib/cmucl/lib/mh-scan,lib/cmucl/lib/spell-
dictionary.bin
Hemlock files.
lib/cmucl/lib/fonts/
X11 fonts for Hemlock.
lib/cmucl/lib/XKeysymDB
Database of X Keysym names for Motif.
lib/cmucl/lib/load-foreign.csh
Script used by LOAD-FOREIGN to run "ld(1,8)" on some platforms.
~/init.lisp,~/.cmucl-init.lisp
User customization files loaded at lisp startup; either name
is acceptable. Init files can be compiled.
~/hemlock-init.lisp,~/.hemlock-init.lisp
Hemlock initialization file(1,n), loaded when Hemlock starts.
SEE ALSO
cmucl(1), README
The ``CMU Common Lisp User's Manual'',
the ``Hemlock User's Manual'', and
the ``Hemlock Command Implementor's Manual''
BUGS
Consult http://www.cons.org/cmucl/support.html for support information,
including mechanisms for bug reporting. Please consult your local CMU
CL maintainer or Common Lisp expert if(3,n) any to verify(1,8) that a problem
really is a bug before reporting it.
Known problems with this version:
-- Detection of stack overflow is not very graceful. You get many
"map failure" errors on stderr.
-- If file(1,n) descriptors are used up, then Lisp will die.
-- Several proposed ANSI Common Lisp (CLtL II) features are not imple-
mented: Any CLOS features not implemented by PCL, and features added
since the first ANSI draft.
-- The interpreter's pre-processing freezes in(1,8) the macro definitions in(1,8)
effect at the time(1,2,n) an interpreted function is defined.
7th Edition October 15, 1991 LISP(1)