ILISP is "free"; this means that everyone is free to use it and free to redistribute it on a free basis. ILISP is not in the public domain; it is copyrighted and there are restrictions on its distribution, but these restrictions are designed to permit everything that a good cooperating citizen would want to do. What is not allowed is to try to prevent others from further sharing any version of ILISP that they might get from you. The precise conditions appears following this section.
The easiest way to get a copy of ILISP is from someone else who has it. You need not ask for permission to do so, or tell any one else; just copy it.
If you do start using the package, please send mail to
ilisp-request@naggum.no to subscribe to the ILISP mailing
list.
Please send bugs, questions or suggestions for discussion to
ilisp@naggum.no. Message sent there will be distributed to
all subscribers.
You can get the distribution file, ilisp-5.8.tar.gz via
anonymous FTP from FTP.CS.CMU.EDU (128.2.206.173) in
/afs/cs/user/campbell/http/ilisp/.
% ftp ftp.cs.cmu.edu Name (ftp.cs.cmu.edu:rickc): anonymous 331 Guest login ok, send username@node as password. Password: your-user-id@your-hostname ftp> cd /afs/cs/user/campbell/http/ilisp 250 Directory path set to /afs/cs/user/campbell/http/ilisp. ftp> type binary 200 Type set to I. ftp> get ilisp-5.8.tar.gz 200 PORT command successful. 150 Opening data connection for ilisp-5.8.tar.gz. 226 Transfer complete. local: ilisp-5.8.tar.gz remote: ilisp-5.8.tar.gz 168801 bytes received. ftp> quit 221 Goodbye.
Or get whatever single files you need from the untarred
subdirectory.
You can also get ilisp-5.8.tar.gz via
anonymous FTP from FTP.ICSI.BERKELEY.EDU in either
/pub/software/elisp/ or /pub/theory/marcoxa/elisp/.
Unpack and install:
% gzip -dc ilisp-5.8.tar.gz | tar xf -
See section How to install ILISP.
You can use the World Wide Web (WWW) to get the distribution file from the anonymous FTP locations using one of the following URLs:
ftp://ftp.cs.cmu.edu/afs/cs/user/campbell/http/ilisp/ilisp-5.8.tar.gz
ftp://ftp.icsi.berkeley.edu/pub/software/elisp/ilisp-5.8.tar.gz
ftp://ftp.icsi.berkeley.edu/pub/theory/marcoxa/ilisp-5.8.tar.gz
You can also use the CMU Artificial Intelligence Repository:
http://www.cs.cmu.edu/Web/Groups/AI/html/repository.html
From there follow: LISP, UTIL, EMACS and finally
ILISP. Use your browser capabilities to download what you
need.
The complete URL for the distribution file in the CMU AI Repository is
http://www.cs.cmu.edu/afs/cs/project/ai-repository/ai/lang/lisp/util/emacs/ilisp/v57/ilisp57.tgz
Other URLs for the distribution file include:
http://www.c2.net/~campbell/ilisp/ilisp-5.8.tar.gz
http://www.cs.cmu.edu/~campbell/ilisp/ilisp-5.8.tar.gz
Unpack and install:
% gzip -dc ilisp-5.8.tar.gz | tar xf -
See section How to install ILISP.
ILISP replaces the standard inferior LISP mode. ILISP is based on comint mode and derived from a number of different interfaces including Symbolics, CMU Common Lisp, and Thinking Machines.
There are many people that have taken the time to report bugs, make suggestions and even better send code to fix bugs or implement new features.
Thanks to Guido Bosch, David Braunegg, Tim Bradshaw, Thomas M. Breuel, Hans Chalupsky, Kimball Collins, Brian Dennis, David Duff, Tom Emerson, Michael Ernst, Scott Fahlman, David Gadbois, Robert P. Goldman, Marty Hall, Richard Harris, Jim Healy, Christopher Hoover, Larry Hunter, Ben Hyde, Chuck Irvine, Michael Kashket, Mark Kantrowitz, Qiegang Long, Erik Naggum, Dan Pierson, Yusuf Pisan, Frank Ritter, Jeffrey Mark Siskind, Neil Smithline, Richard Stallman, Larry Stead, Jason Trenouth, Christof Ullwer, Bjorn Victor, Fred White, Ben Wing, Matsuo Yoshihiro, Jamie Zawinski, Paul Fuqua (for the CMU-CL GC display code) and Marco Antoniotti for bug reports, suggestions and code. Our apologies to anyone we may have forgotten.
Special thanks to Todd Kaufmann for the texinfo file, work on bridge, epoch-pop and for really exercising everything.
Please send bug reports, fixes and extensions to
ilisp@naggum.no so that they can be merged into the master
source.
--Chris McConnell 18-Mar-91 --Ivan Vazquez 27-Jun-93 --Marco Antoniotti and Rick Campbell 25-Oct-96
ILISP is an interface from GNU Emacs to an inferior LISP. It has the following features:
Installation of ILISP and some initialization of your computing environment are described in this chapter. Please read the following sections carefully before getting started with ILISP.
If ILISP has already been installed at your location, you can probably skip ahead to "Autoloading."
Note that Jamie Zawinki's byte-compiler is required when compiling
ILISP. If you don't have it, get it from
ftp://archive.cis.ohio-state.edu/pub/gnu/emacs/elisp-archive/bytecomp2.tar.Z
You don't need it if you are running emacs version 19 as both the FSF and XEmacs releases include this in their distributions.
Some configuration needs to be done before compiling the emacs-lisp
files that comprise ILISP. This should be done in the
Makefile file in the section of the file marked
CONFIGURATION SECTION.
First, set the YOUR_EMACS variable to be the pathname of the
emacs you will be using ILISP with. This is the emacs that will be used
to compile ILISP with.
If you don't have Jamie Zawinski's byte compiler in your standard load
path ( both FSF's 19 and XEmacs 19 do have enhaced versions of it )
then you will have to uncomment the BYTECOMP line and set it to
point to the correct location of the bytecomp files.
If you do not have comint already in your emacs ( both FSF 19 and XEmacs
19 do ) then uncomment the USE_BUNDLED_COMINT line. This will
cause the copy of comint.el to be moved from the Extras
directory into the main ILISP directory.
The advice section is left uncommented out in the distributed
Makefile because most people will not have
advice.elc in their load path. Only XEmacs will have
this in the standard distribution. If you do have it in your load path,
then to avoid having two copies in your load-path and avoiding future
confusion then comment out both the ADVICE and
USE_BUNDLED_ADVICE lines.
You can then compile everything with the shell command
% make -f Makefile-ilisp <your target here>
Where the possible targets are emacs_18, emacs_18_epoch,
emacs_18_menu, and emacs_19.
Ignore any compilation warnings unless they result in ILISP not compiling completely.
You should then copy relevant sections of ilisp.emacs to your
.emacs or to the system-wide default.el file, depending on
who will be using ILISP.
You should add the directory where all of the ILISP emacs-lisp files
reside to your load-path. There is an example of this in
ilisp.emacs
As an alternative you could set up a .ilisp which contains the
appropriate portions of ilisp.emacs, in order to avoid cluttering
too much .emacs or default.el
The first time a dialect is started, the interface files will complain
about not being compiled, just hit i to ignore the message. Once
a lisp dialect is started up, you should execute the command
ilisp-compile-inits which will compile the `*.lisp' files
and write them to the same directory as the ilisp files.
The binary files should have a unique
extension for each different combination of architecture and
LISP dialect. You will need to change
ilisp-init-binary-extension and
ilisp-init-binary-command to get additional
extensions. The binary for each different architecture
should be different. If you want to build the interface
files into a LISP world, you will also need to set
ilisp-load-inits to nil in the same place that
you change ilisp-program to load the LISP
world.
There is an ilisp-site-hook for initializing site specific stuff
like program locations when ILISP is first loaded. You may want to
define appropriate autoloads in your system Emacs start up file.
Example site init:
;;; CMU site
(setq ilisp-site-hook
'(lambda ()
(setq ilisp-motd "CMU ILISP V%s")
(setq expand-symlinks-rfs-exists t)
(setq allegro-program "/usr/misc/.allegro/bin/cl")
(setq lucid-program "/usr/misc/.lucid/bin/lisp")))
The files you need to use ilisp are:
ilisp-lispm-bindings.
A complete example of things you may want to add to your .emacs
can be found in the in the file `ilisp.emacs' in the
ilisp-directory what follows is that file.
;;;
;;; This file shows examples of some of the things you might want to
;;; do to install or customize ILISP. You may not want to include all
;;; of them in your .emacs. For example, the default key binding
;;; prefix for ILISP is C-z and this file changes the default prefix to
;;; C-c. For more information on things that can be changed, see the
;;; file ilisp.el.
;;;
;;; If ilisp lives in some non-standard directory, you must tell emacs
;;; where to get it. This may or may not be necessary.
(setq load-path (cons (expand-file-name "~jones/emacs/ilisp/") load-path))
;;; If you always want partial minibuffer completion
(require 'completer)
;;; If you want to redefine typeout-window keys:
(add-hook 'ilisp-load-hook
'(lambda ()
(define-key global-map "\C-c1" 'ilisp-bury-output)
(define-key global-map "\C-cv" 'ilisp-scroll-output)
(define-key global-map "\C-cg" 'ilisp-grow-output)))
(autoload 'run-ilisp "ilisp" "Select a new inferior LISP." t)
;;; Autoload based on your LISP. You only really need the one you use.
;;; If called with a prefix, you will be prompted for a buffer and
;;; program.
;;;
;;; [Back to the old way now -- Ivan Mon Jun 28 23:30:51 1993]
;;;
(autoload 'clisp "ilisp" "Inferior generic Common LISP." t)
(autoload 'allegro "ilisp" "Inferior Allegro Common LISP." t)
(autoload 'lucid "ilisp" "Inferior Lucid Common LISP." t)
(autoload 'cmulisp "ilisp" "Inferior CMU Common LISP." t)
(autoload 'kcl "ilisp" "Inferior Kyoto Common LISP." t)
(autoload 'akcl "ilisp" "Inferior Austin Kyoto Common LISP." t)
(autoload 'ibcl "ilisp" "Ibuki Common LISP." t)
(autoload 'scheme "ilisp" "Inferior generic Scheme." t)
(autoload 'oaklisp "ilisp" "Inferior Oaklisp Scheme." t)
;;; Define where LISP programs are found. (This may already be done
;;; at your site.)
(setq allegro-program "/usr/misc/.allegro/bin/cl")
(setq lucid-program "/usr/misc/.lucid/bin/lisp")
(setq cmulisp-program "/usr/misc/.cmucl/bin/lisp")
;;; If you run cmu-cl then set this to where your source files are.
(setq cmulisp-local-source-directory
"/usr/local/utils/CMU-CL/")
;;; This makes reading a lisp file load in ilisp.
(set-default 'auto-mode-alist
(append '(("\\.lisp$" . lisp-mode)) auto-mode-alist))
(setq lisp-mode-hook '(lambda () (require 'ilisp)))
;;; Sample load hook
(add-hook 'ilisp-load-hook
'(lambda ()
;; Change default key prefix to C-c
(setq ilisp-prefix "\C-c")
;; Define LispMachine-like key bindings, too.
(ilisp-lispm-bindings)
;; Sample initialization hook. Set the inferior LISP directory to
;; the directory of the buffer that spawned it on the first prompt.
(setq ilisp-init-hook
'(lambda ()
(default-directory-lisp ilisp-last-buffer)))))
To start a Lisp use M-x run-ilisp, or a specific dialect like M-x allegro. If called with a prefix you will be prompted for a buffer name and a program to run. The default buffer name is the name of the dialect. The default program for a dialect will be the value of DIALECT-program or the value of ilisp-program inherited from a less specific dialect. If there are multiple LISP's, use the dialect name or M-x select-ilisp (C-z S) to select the current ILISP buffer.
Entry into ILISP mode runs the hooks on comint-mode-hook and
ilisp-mode-hook and then DIALECT-hooks specific to LISP
dialects in the nesting order above. Many dialects call
ilisp-load-init in their dialect setup.
These are the currently supported dialects.
The dialects are listed so that the indentation correponds to the hierarchical relationship between dialects.
clisp
allegro
lucid
kcl
akcl
gcl
ecl
ibcl
cmulisp
clisp-hs
lispworks
scheme
oaklisp
If anyone figures out support for other dialects I would be happy to include it in future releases. See section Dialects.
To define a new dialect, See section Defining new dialects and See section ILISP Customization.
*dialect*
lisp-mode-buffers
lisp-source-modes. If it's loaded into a buffer that is
in one of these major modes, it's considered a lisp source file by
find-file-lisp, load-file-lisp and
compile-file-lisp.
Used by these commands to determine defaults.
*Completions**Aborted Commands*
*Errors*
*Output*
*Error Output*
*ilisp-send*
*Edit-Definitions*
*All-Callers*
*Last-Changes*
*Changed-Definitions*
All ILISP output is funneled through the function which is bound to
the hook ilisp-display-output-function. The function gets
a single argument, a string, and should make that output visible to
the user somehow.
One possible choice for output display is
ilisp-display-output-in-typeout-window,
which pops up a window at the top of the current screen which is
just large enough to display the output. This window can be
"remote controlled" by the commands ilisp-scroll-output,
ilisp-bury-output, and ilisp-grow-output.
Unlike the old popper facility, the ilisp typeout window facility does not trounce on any existing Emacs functions or on any common key bindings, like C-x o.
Other built-in functions which might be useful as values for
ilisp-display-output-function include
ilisp-display-output-default,
ilisp-display-output-adaptively,
ilisp-display-output-in-lisp-listener,
ilisp-display-output-in-temp-buffer, and
ilisp-display-output-in-typeout-window.
The default display function is ilisp-display-output-default,
which obeys the lisp-no-popper variable.
Users are encouraged to write their own output display functions to get the exact desired behavior, displaying on a private emacs screen, in a pop-up dialog box, or whetever.
An alternative to typeout windows is to always have the inferior LISP
buffer visible and have all output go there. Setting
lisp-no-popper to t will cause all output to go to the
inferior LISP buffer. Setting lisp-no-popper to 'message
will make output of one line go to the message window. Setting
comint-always-scroll to t will cause process output to
always be visible. If a command gets an error, you will be left in the
break loop.
Commands to make switching between buffers easier.
pop-up-windows to nil.
Most of these key bindings work in both Lisp Mode and ILISP mode. There are a few additional and-go bindings found in Lisp Mode.
In LISP, the major unit of interest is a form, which is anything between two matching parentheses. Some of the commands here also refer to "defun," which is a list that starts at the left margin in a LISP buffer, or after a prompt in the ILISP buffer. These commands refer to the "defun" that contains the point.
"A call" refers to a reference to a function call for a function or macro, or a reference to a variable. Commands which "insert a call" in the ILISP buffer will bring up the last command which matches it or else will insert a template for a call.
When an eval is done of a single form matching ilisp-defvar-regexp
the corresponding symbol will be unbound and the value assigned again.
When you send a form to LISP, the status light will reflect the
progress of the command. In a lisp mode buffer the light will reflect
the status of the currently selected inferior LISP unless
lisp-show-status is nil. If you want to find out what command is
currently running, use the command C-z s (status-lisp).
If you call it with a prefix, the pending commands will be displayed as
well.
Note that in this table as elsewhere, the key C-z (ilisp-prefix) is used as a prefix character for ILISP commands, though this may be changed. For a full list of key-bindings, use M-x describe-mode or M-x describe-bindings while in an ILISP-mode buffer.
The eval/compile commands verify that their expressions are balanced and then send the form to the inferior LISP. If called with a positive prefix, the result of the operation will be inserted into the buffer after the form that was just sent.
For commands which operate on a region, the result of the compile or eval is the last form in the region.
The `and-go' versions will perform the operation and then
immediately switch to the ILISP buffer where you will see the results of
executing your form. If eval-defun-and-go-lisp or
compile-defun-and-go-lisp is called with a prefix, a call for the
form will be inserted as well.
ilisp-prefix.
compile-defun-lisp is called in an inferior LISP buffer with
no current form, the last form typed to the top-level will be compiled.
If any of the forms contain an interactive command, then the command
will never return. To get out of this state, you need to use
abort-commands-lisp (C-z g). If lisp-wait-p
is t, then EMACS will display the result of the command in the
minibuffer or a pop-up window. If lisp-wait-p is nil,
(the default) the send is done asynchronously and the results will be
brought up only if there is more than one line or there is an error. In
this case, you will be given the option of ignoring the error, keeping
it in another buffer or keeping it and aborting all pending sends. If
there is not a command already running in the inferior LISP, you can
preserve the break loop. If called with a negative prefix, the sense of
lisp-wait-p will be inverted for the next command.
describe-lisp, inspect-lisp, arglist-lisp, and
documentation-lisp switch whether they prompt for a response or
use a default when called with a negative prefix. If they are
prompting, there is completion through the inferior LISP by using
TAB or M-TAB. When entering an expression in the
minibuffer, all of the normal ilisp commands like arglist-lisp
also work.
Commands that work on a function will use the nearest previous function symbol. This is either a symbol after a `#'' or the symbol at the start of the current list.
C-z a (arglist-lisp)
C-z d (documentation-lisp)
C-z i (describe-lisp)
C-z i (describe-lisp)
C-z I (inspect-lisp)
C-z D (fi:clman)
C-z A (fi:clman-apropos)
fi:clman-apropos will get information apropos
a specific string. Some of the documentation is specific to the allegro
dialect, but most of it is for standard Common LISP.
The first time an inferior LISP mode command is executed in a Lisp Mode
buffer, the package will be determined by using the regular expression
ilisp-package-regexp to find a package sexp and then passing that
sexp to the inferior LISP through ilisp-package-command.
For the `clisp' dialect, this will find the first (in-package
PACKAGE) form in the file.
A buffer's package will be displayed in the mode line.
If a buffer has no
specification, forms will be evaluated in the current inferior LISP
package.
Buffer package caching can be turned off by setting the variable
lisp-dont-cache-package to T. This will force ILISP to
search for the closest previous ilisp-package-regexp in the
buffer each time an inferior LISP mode command is executed.
C-z p (package-lisp)
C-z P (set-package-lisp)
M-x set-buffer-package-lisp
The following commands all deal with finding things in source code. The first time that one of these commands is used, there may be some delay while the source module is loaded. When searching files, the first applicable rule is used:
lisp-source-modes or all files
defined using lisp-directory.
M-x lisp-directory defines a set of files to be
searched by the source code commands. It prompts for a directory and
sets the source files to be those in the directory that match entries
in auto-mode-alist for modes in lisp-source-modes.
With a positive
prefix, the files are appended. With a negative prefix, all current
buffers that are in one of lisp-source-modes will be searched. This
is also what happens by default. Using this command stops using a
tags file.
edit-definitions-lisp, who-calls-lisp, and
edit-callers-lisp will switch whether they prompt for a response
or use a default when called with a negative prefix. If they are
prompting, there is completion through the inferior LISP by using
TAB or M-TAB. When entering an expression in the
minibuffer, all of the normal ILISP commands like arglist-lisp
also work.
edit-definitions-lisp (M-.) will find a
particular type of definition for a symbol. It tries to use the rules
described above. The files to be searched are listed in the buffer
*Edit-Definitions*. If lisp-edit-files is nil, no search will be
done if not found through the inferior LISP. The variable
ilisp-locator contains a function that when given the name and type
should be able to find the appropriate definition in the file. There
is often a flag to cause your LISP to record source files that you
will need to set in the initialization file for your LISP. The
variable is *record-source-files* in both allegro and lucid. Once a
definition has been found, next-definition-lisp
(M-,) will find the next definition
(or the previous definition with a prefix).
edit-callers-lisp (C-z ^) will generate a list of all
of the callers of a function in the current inferior LISP and edit the
first caller using edit-definitions-lisp. Each successive call to
next-caller-lisp (M-`) will edit the next caller
(or the previous caller with a prefix). The list is stored in the
buffer *All-Callers*. You can also look at the callers by doing
M-x who-calls-lisp.
search-lisp (M-?) will search the current tags files,
lisp-directory files or buffers in one of lisp-source-modes for a
string or a regular expression when called with a prefix.
next-definition-lisp (M-,) will find the next definition
(or the previous definition with a prefix).
replace-lisp (M-") will replace a string (or a regexp with
a prefix) in the current tags files, lisp-directory files or
buffers in one of lisp-source-modes.
Here is a summary of the above commands (behavior when given prefix argument is given in parentheses):
M-x lisp-directory
M-. (edit-definitions-lisp)
M-, (next-definition-lisp)
C-z ^ (edit-callers-lisp)
M-` (next-caller-lisp)
edit-callers-lisp.
M-x who-calls-lisp
M-? (search-lisp)
lisp-directory files or buffers. Use next-definition-lisp
to find next occurence.
M-" (replace-lisp)
The following commands all deal with making a number of changes all at once. The first time one of these commands is used, there may be some delay as the module is loaded. The eval/compile versions of these commands are always executed asynchronously.
mark-change-lisp (C-z SPC) marks the current defun as
being changed. A prefix causes it to be unmarked. clear-changes-lisp
(C-z * 0) will clear all of the changes.
list-changes-lisp (C-z * l) will show the forms
currently marked.
eval-changes-lisp (C-z * e), or
compile-changes-lisp (C-z * c) will
evaluate or compile these changes as appropriate.
If called with a positive prefix, the changes will be kept.
If there is an error, the process will stop and show the error
and all remaining changes will remain in the list. All of the results
will be kept in the buffer *Last-Changes*.
Summary:
C-z SPC (mark-change-lisp)
C-z * e (eval-changes-lisp)
C-z * c (compile-changes-lisp)
C-z * 0 (clear-changes-lisp)
C-z * l (list-changes-lisp)
File commands in lisp-source-mode buffers keep track of the last used
directory and file. If the point is on a string, that will be the
default if the file exists. If the buffer is one of
lisp-source-modes, the buffer file will be the default. Otherwise,
the last file used in a lisp-source-mode will be used.
default-directory to the LISP default directory.
There are two keyboard modes for interacting with the inferior LISP, \"interactive\" and \"raw\". Normally you are in interactive mode where keys are interpreted as commands to EMACS and nothing is sent to the inferior LISP unless a specific command does so. In raw mode, all characters are passed directly to the inferior LISP without any interpretation as EMACS commands. Keys will not be echoed unless ilisp-raw-echo is T.
Raw mode can be turned on interactively by the command
raw-keys-ilisp (C-z #) and will continue until you
type C-g. Raw mode can also be turned on/off by inferior LISP
functions if the command io-bridge-ilisp (M-x io-bridge-ilisp)
has been executed in the inferior LISP either interactively or on a
hook. To turn on raw mode, a function should print ^[1^] and to turn
it off should print ^[0^]. An example in Common LISP would be:
(progn (format t "1 ") (print (read-char)) (format t "0 "))
If you want to abort the last command you can use C-g.
If you want to abort all commands, you should use the command
abort-commands-lisp (C-z g). Commands that are
aborted will be put in the buffer *Aborted Commands* so that
you can see what was aborted. If you want to abort the currently
running top-level command, use interrupt-subjob-ilisp (C-c
C-c). As a last resort, M-x panic-lisp will reset the ILISP
state without affecting the inferior LISP so that you can see what is
happening.
delete-char-or-pop-ilisp (C-d) will delete
prefix characters unless you are at the end of an ILISP buffer in
which case it will pop one level in the break loop.
reset-ilisp, (C-z z) will reset the current inferior
LISP's top-level so that it will no longer be in a break loop.
Summary:
If lisp-wait-p is nil (the default),
all sends are done asynchronously and the results will be
brought up only if there is more than one line or there is an error.
In case, you will be given the option of ignoring the error, keeping
it in another buffer or keeping it and aborting all pending sends.
If there is not a command already running in the inferior LISP, you can
preserve the break loop. If called with a negative prefix, the sense of
lisp-wait-p will be inverted for the next command.
ILISP mode is built on top of comint-mode, the general
command-interpreter-in-a-buffer mode. As such, it inherits many
commands and features from this, including a command history mechanism.
Each ILISP buffer has a command history associated with it. Commands
that do not match ilisp-filter-regexp and that are longer than
ilisp-filter-length and that do not match the immediately prior
command will be added to this history.
See comint-mode documentation for more information on
`comint' commands.
Commands to reduce number of keystrokes.
ilisp-prefix-match is set to t.
(If you set it to t, inferior LISP completions will be faster.)
With partial completion, `p--n' would complete to
`position-if-not' in Common LISP.
If the symbol follows a left paren or a `#'', only symbols with
function cells will be considered.
If the symbol starts with a `*' or you call with a
positive prefix all possible completions will be considered.
Only external symbols are considered if there is a package qualification
with only one colon.
The first time you try to complete a string the longest common substring
will be inserted and the cursor will be left
on the point of ambiguity.
If you try to complete again, you can see the possible completions.
If you are in a string, then filename completion will be done instead.
And if you try to complete a filename twice, you will see a list of
possible completions.
Filename components are completed individually, so `/u/mi/' could
expand to `/usr/misc/'.
If you complete with a negative
prefix, the most recent completion (symbol or filename) will be undone.
Indentation, parenthesis balancing, and comment commands.
comment-start before and
comment-end's after the lines in region. To uncomment a region,
use a minus prefix.
Starting a dialect runs the hooks on comint-mode-hook
and ilisp-mode-hook and then DIALECT-hooks specific
to dialects in the nesting order below.
clisp
allegro
lucid
kcl
akcl
ibcl
cmulisp
scheme
oaklisp
On the very first prompt in the inferior LISP,
the hooks on ilisp-init-hook are run. For more information on
creating a new dialect or variables to set in hooks, see `ilisp.el'.
ilisp-site-hook
ilisp-load-hook
ilisp-mode-hook
ilisp-init-hook
DIALECT-hook
Variables you might want to set in a hook or dialect:
ilisp-prefix
ilisp-program
ilisp-motd
lisp-wait-p
ilisp-handle-errors
ilisp-display-output-function
lisp-no-popper
lisp-show-status
ilisp-prefix-match
ilisp-filter-regexp
ilisp-filter-length
ilisp-other-prompt
A dialect of lisp is a specific implementation. For the parts of Common Lisp which are well specified, they are usually the same. For the parts that are not (debugger, top-level loop, etc.), there is usually the same functionality but different commands.
ILISP provides the means to specify these differences so that the ILISP commands will use the specific command peculiar to an implementation, but still offer the same behavior with the same interface.
To define a new dialect use the macro defdialect. For examples,
look at the dialect definitions in `ilisp-acl.el',
`ilisp-cmu.el', `ilisp-kcl.el', `ilisp-luc'. There are
hooks and variables for almost anything that you are likely to need to
change. The relationship between dialects is hierarchical with the root
values being defined in setup-ilisp. For a new dialect, you only
need to change the variables that are different than in the parent
dialect.
Basic tools for creating new commands:
deflocal
ilisp-dialect
lisp-symbol
lisp-symbol-name
lisp-symbol-delimiter
lisp-symbol-package
lisp-string-to-symbol
lisp-symbol-to-string
lisp-buffer-symbol
lisp-previous-symbol
lisp-previous-sexp
lisp-def-name
lisp-function-name
ilisp-read
ilisp-read-symbol
ilisp-completing-read
Notes:
ilisp-send to send a
message to the inferior LISP.
eval-region-lisp or
compile-region-lisp.
*Aborted Commands* buffer, *Aborted Commands* buffer
*All-Callers* buffer, *All-Callers* buffer
*Changed-Definitions* buffer
*Completions* buffer
*Edit-Definitions* buffer, *Edit-Definitions* buffer
*Error Output* buffer
*Errors* buffer
*ilisp-send* buffer
*Last-Changes* buffer, *Last-Changes* buffer
*Output* buffer
comint-mode
Commands available via M-x prefix.
Variables and hooks of ILISP.
Internal functions of ILISP which can be used to write new commands.
This document was generated on 26 October 1996 using the texi2html translator version 1.51.