eho@clarity.Princeton.EDU (Eric Ho) (09/07/89)
The current version of clisp (as of August 89') doesn't mix with monkey.el (monkey version is as of June 89'). If you load monkey.el and then load clisp.el and then when you invoke (start-lisp) then your *lisp* buffer will be seriously choked -- you can type in anything including <CR>'s. If you load clisp.el before monkey.el then you're ok. It is weird. However, if you're using earler version of clisp.el (say around March 89') then you're ok no matter what you load first. Also, but the latest and the March version of clisp.el barfs when your lisp filename extension is .l instead of .lsp or .lisp -- it barfs when you do a 'C-c l' after you've visited your .l file. -- Eric Ho Cognitive Science Lab., Princeton University voice = 609-987-2987 email = eho@confidence.princeton.edu 609-987-2819 (messages) eho@bogey.princeton.edu regards. -eric-
eho@clarity.Princeton.EDU (Eric Ho) (09/07/89)
The current version of clisp (as of August 89') doesn't mix with monkey.el
(monkey version is as of June 89'). If you load monkey.el and then load
clisp.el and then when you invoke (start-lisp) then your *lisp* buffer will be
seriously choked -- you can type in anything including <CR>'s.
If you load clisp.el before monkey.el then you're ok. It is weird. However,
if you're using earler version of clisp.el (say around March 89') then you're
ok no matter what you load first.
Also, both the latest and the March version of clisp.el barfs when your lisp
filename extension is .l instead of .lsp or .lisp (assuming of course ("\\.l$"
. lisp-mode)) is in aut-mode-alist just like that for .lsp or .lisp -- it
barfs when you do a 'C-c l' after you've visited your .l file.
--
Eric Ho
Cognitive Science Lab., Princeton University
voice = 609-987-2987 email = eho@confidence.princeton.edu
609-987-2819 (messages) eho@bogey.princeton.edu
regards.
-eric-