comparison lisp/ilisp/README @ 4:b82b59fe008d r19-15b3

Import from CVS: tag r19-15b3
author cvs
date Mon, 13 Aug 2007 08:46:56 +0200
parents 376386a54a3c
children
comparison
equal deleted inserted replaced
3:30df88044ec6 4:b82b59fe008d
1 -*- Mode: Text -*- 1 ILISP is a powerful GNU Emacs interface to many dialects of Lisp,
2 including Lucid, Allegro, Harlequin LispWorks, GCL, KCL, AKCL, ECL, IBCL,
3 and CMUCL.
2 4
3 ILISP is a powerful GNU Emacs interface to many dialects of Lisp,
4 including Lucid, Allegro, Harlequin LispWorks, KCL, AKCL, ECL, IBCL,
5 and CMUCL.
6 Written by Chris McConnell <ccm+@cs.cmu.edu> and now maintained by 5 Written by Chris McConnell <ccm+@cs.cmu.edu> and now maintained by
7 Marco Antoniotti <marcoxa@cs.nyu.edu> and Rick Busdiecker <rfb@lehman.com>. 6 Marco Antoniotti <marcoxa@icsi.berkeley.edu> and
7 Rick Campbell <campbell@c2.net>.
8 8
9 Please refer to the following files in this directory: 9 Please refer to the following files in this directory:
10 HISTORY - A detailed summary of changes over the course of ILISP's 10 HISTORY: A detailed summary of changes over the course of ILISP's
11 existence. 11 existence.
12 GETTING-ILISP - Directions for obtaining this collection using 12 GETTING-ILISP: Directions for obtaining this collection using
13 anonymous FTP. 13 anonymous FTP.
14 INSTALLATION: Directions about how to install ILISP and specific
15 dialect needs.
14 16
15 Please send bug reports, questions, suggestions, etc. to: 17 Please send bug reports, questions, suggestions, etc. to:
16 ILISP Discussion <ilisp@lehman.com> 18 ILISP Discussion <ilisp@naggum.no>
17 19
18 Please address all list administration messages, such as requests to 20 Please address all list administration messages, such as requests to
19 subscribe or unsubscribe from ilisp@lehman.com, to: 21 subscribe or unsubscribe from ilisp@naggum.no, to:
20 ILISP Administrivia <ilisp-request@lehman.com> 22 ILISP Administrivia <ilisp-request@naggum.no>
21 23
22 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 24 See http://www.c2.net/~campbell/ilisp/ or
23 25 http://www.cs.cmu.edu/~campbell/ilisp/ for more information.
24 Future developments:
25
26 ILISP might become part of the standard FSF distribution in the
27 future. There are numerous little things that need to be done in that
28 direction in order to conform to FSF coding and interface standards
29 (e.g. the behavior of C-a is not acceptable by the FSF interface
30 standard and numerous doc strings in ILISP need to be rewritten).
31 This will happen slowly over the next(s) releases.
32
33 Thanks go to the following people (and to many others who need our
34 apologies for having let them out of the list):
35
36 Tim Bradshaw <tfb@edinburgh.ac.uk>
37 Kimball Collins <kpc@ptolemy-ethernet.arc.nasa.gov>
38 David Gadbois <gadbois@mcc.com>
39 Robert P. Goldman <goldman@src.honeywell.com>
40 Marty Hall <hall@aplcenmp.apl.jhu.edu>
41 Richard Harris <rharris@chestnut.com>
42 Christopher Hoover <ch@lks.csi.com>
43 Larry Hunter <hunter@work.nlm.nih.gov>
44 Todd Kaufmann <toad+@cs.cmu.edu>
45 Mark Kantrowitz <mkant+@cs.cmu.edu>
46 Qiegang Long <qlong@luke.cs.umass.edu>
47 Christopher McConnell <ccm@HITECH.CHESS.CS.CMU.EDU>
48 Yusuf Pisan <yusuf@SPD-13.ils.nwu.edu>
49 Jeffrey Mark Siskind <qobi@qobi.ai.toronto.edu>
50 Richard Stallman <rms@gnu.ai.mit.edu>
51 Jason Trenouth <jason@harlequin.co.uk>
52 Christof Ullwer <Ullwer@informatik.uni-stuttgart.de>
53 Ivan Vazquez <ivan@darwin.bu.edu>
54 Matsuo Yoshihiro <yosihiro@nttkb.ntt.jp>