Instructions for getting acquainted with Emacs.
The complications in starting ACL in xemacs seem to stem
interaction between cse and the localhost. Here's my attempt to explain
how to make it work. First, log in to the localhost (your cse logon will
work). Then, copy the .emacs file from the website to your home
directory*, then start xemacs from the KDE bar (it's under the dinosaur,
then the top choice, then editors, then text, then emacs clones, then
xemacs). After that is done, you should be able to type ESC-x
fi:common-lisp and it should work. If it doesn't, then make sure the
.emacs is in your home directory, restart it, make sure you have the path
line (in one of the emails sent out) in your .cshrc file and things like
that. Good luck...
*Your home directory is the same as your cse home directory,
enough. You can copy this file just using any text editor and pasting the
text in, then saving it as .emacs. If you do this in emacs, then restart
emacs afterwards, of course. Also, don't start emacs from the terminal
window in the KDE screen. Use the dinosaur. If you start it from the
terminal, it will run the CSE emacs, and will not be able to find lisp. To
make sure you're in the right place, you can call up the KDE file manager
(it's about 2 buttons away from the dinosaur), and go to /usr/dist/pkgs
and see if the acl150 is there. Also note, in the path to put in the
.cshrc file, it's an L, not a 1.
/ \_ CH2 -O- C - CH2 - CH2 - CH3
\ __ /
Stop and smell the Roses!
ACL has a great interactive development environement with a graphical inspector, debugger, profiler (time and space), etc. etc. To use, you hsould first type in the lisp environment:
(composer:start-composer) alternatively choose "Start composer" from the menu buttons of emacs/.Warning: you may need to tell X to allow composer to open up windows. For this purpose, you need to type "xhost +" before you start xemacs, then ACL, then composer...