From: Simon Leinen

Subject: Re: acl5 Linux and Xemacs

Date: 1998-7-17 11:23

> Its very first line says > (requires 'cl) > which means, if I am right, that a lisp image is required. But so > far I do not have a lisp image. Let me go on with the *.el files > for the moment.
No, "(require 'cl)" asks Emacs to load the cl.el Emacs-Lisp package, which contains many Common-Lisp-like functions for GNU Emacs. It shouldn't cause you any problems if your Emacs is properly installed.
> When loading from a scratch buffer the fi-site-init file, the local > buffer message is > Invalid read syntax: "#" > But never mind, let's go on.
This is bad. Either a hash mark slipped in fi-site-init or one of the files loaded through it, or the .elc (Emacs Lisp byte-code) files have been compiled using a different version of Emacs from the one in which you are trying to load them. Remove the *.elc files and try to remake them using "make", after verifying that the Makefiles specifies the correct version of emacs. I highly recommend to load the package via fi-site-init.el, because that will ensure that all necessary modules are loaded in the right order.
> Now I would like to test if the Emacs-Lisp Interface is ok. For that > I need the form fi:verify-emacs-support which is in > /usr/local/acl5/eli/fi-utils.el. > > After loading the file and evaluating the form I get the message > everything looks fine! > That I still dont believe. > > The fi:common-lisp form is in the /usr/local/acl5/eli/fi-subproc.el file. > > Here I must admit that I did not succeed to automize these loading > operations in the .emacs file. For a reason I don't understand I > must do by hand in a scratch buffer, or with the M-x load-file > command. It is really not clear what I am doing wrong ...
The ~/.emacs file should be loaded when you start Emacs. However, if there are any errors in this file, the remaining code will be skipped (after an error message is displayed). -- Simon Leinen <babar.switch.ch at simon> SWITCH http://www.switch.ch/misc/leinen/ Who is General Failure & why's he reading my disk?