marick@ccvaxa.UUCP (02/11/85)
(If anyone at uiucdcs reads this, could they drop me a note? Thanks.)
I earlier asked whether Unipress Emacs or CCA Emacs was better for editing
LISP. Our link to the USENET is flakey, and I don't believe my message
got out there, so I got fewer replies than expected, all from the ARPANET.
Thanks to all who did reply.
Summary:
Several people pointed out that Unipress Emacs is Gosling Emacs.
True, but I need the Lisp support to be a part of the supported product.
For my purposes, it is not enough that I can add our MLISP functions
to Unipress Emacs. I should have mentioned that.
We will be getting literature from CCA and Unipress, as well as a
copy of Unipress Emacs. I'll post an evaluation later.
The messages themselves:
=================================================================
From: thomas%utah-gr@utah-cs (Spencer W. Thomas)
Unipress Emacs IS Gosling Emacs.
=================================================================
From: Gene Lege' <ots!gene@rice.ARPA>
Brian,
CCA-EMACS does have such an interface to their ELISP interpreter.
I know that it is possible to start up an interactive interpreter
in a special type of buffer called the minibuffer. Interactive
ELISP code may then be entered and tested on text in a normal buffer
in another window.
Unfortunately I can not give a personel evaluation of ELISP because
I have not been able to bring it up on our processor (a Pyramid 90x).
The author of ELISP made the classic mistake of assuming that the
only architecture in the world is a VAX. Just to save two lousy
bytes on every string, he assumes that it is legal to cast a halfword
address into pointer to (unsigned) long. The 90x does not currently
support this alignment (Pyramid is considering modifying their micro-
code to do so, but the last time I checked the decision had not been
made one way or the other.)
Overall, We have been very pleased with CCA-EMACS. If I ever
get around to fixing the brain damage, I'll post it to the net.
Gene Lege'
=================================================================
From: William LeFebvre <phil@rice.ARPA>
Unipress Emacs basically is Gosling's Emacs. They have been hacking on
it alot, so I guess you really have to say that it is a superset of
Gosling's, but they started with Gosling's Emacs. Anything that works
with Gosling's will work with Unipress (at least that's the theory).
William LeFebvre
Department of Computer Science
Rice University
<phil@Rice.arpa>
=================================================================
From:
decwrl!dec-rhea!dec-vaxuum!dyer (Gweeping Gizzards!!!) <decwrl!dec-rhea!dec-vaxuum!dyer@su-shasta.arpa>
MIT has come up with an EMACS/LISP for the VAX running VMS. They
call the new EMACS "STEVE" and the new LISP "NIL". It's very similar to
TOPS-20 EMACS/MACLISP.
<_Jym_Dyer_>
=================================================================
From: Web Dove <dove@MIT-BUGS-BUNNY.ARPA>
The process.ml macro sets up the facilities for putting a lisp or a
shell in a separate window. One word of warning: with my version of
process.ml, if you cause the shell to exit (via ^D) or kill the
process (kill-process lisp) gemacs goes wild looking for it as long
as the buffer it was in exists (i.e. it chews up lots of cpu time).
Be sure you delete the buffer the process was in if the process exits
(or fix the process handling).
=================================================================