Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!iuvax!pur-ee!uiucdcs!uiucdcsb!kadie
From: kadie@uiucdcsb.cs.uiuc.edu
Newsgroups: comp.lang.lisp
Subject: Has anyone fixed Lucid?
Message-ID: <168700005@uiucdcsb>
Date: Wed, 11-Nov-87 17:49:00 EST
Article-I.D.: uiucdcsb.168700005
Posted: Wed Nov 11 17:49:00 1987
Date-Received: Sat, 14-Nov-87 15:34:51 EST
Lines: 39
Nf-ID: #N:uiucdcsb:168700005:000:1389
Nf-From: uiucdcsb.cs.uiuc.edu!kadie    Nov 11 16:49:00 1987



I have been trying for about a month to use Sun (Lucid)
Common Lisp Development Environment (version 2.02).

As anyone using a Lucid Development Lisp figured out how to:

(Editor)
Use the function keys -- It seems that the windowing system
    ignores the function keys of the Sun console completely.

Evaluate a region of a editor buffer and see the results
    -- I can evaluate, but it doesn't display the results.

(Lisp)
Handle errors -- To quote from Steele p. 428
   "...Common Lisp provides ... no standard way to handle errors. Of
    course a complete Lisp ssytem requires error-handling mechanisms."
   "An implementation may also choose to provide means (such as the ERRSET
   special form ...) for a program to trap all errors and prevent the
   debugger from stepping in for certain errors.

Load files without giving a path name -- To quote again from Steele p. 188
   "REQUIRE module-name &optional pathname
    ...
   If the pathname argument is NIL or is not provided, the system will
   attempt to determine, in some system-dependent manner, which files
   to load.
Compile only those Lisp files that have changed -- Like UNIX's Make
   and Symbolics/TI's system.


-------------
Carl Kadie
Inductive Learning Group
University of Illinois at Urbana-Champaign
UUCP: {ihnp4,pur-ee,convex}!uiucdcs!kadie
CSNET: kadie@UIUC.CSNET
ARPA: kadie@M.CS.UIUC.EDU (kadie@UIUC.ARPA)