Re: Emacs load-path after update

[Kai Großjohann]

Ole Andre Birkedal <oandre-b@online.no> writes:

> I downloaded the latest version of Emacs from
> CVS which is 21.3.50.2 and compiled it from source.
> My previous version was 21.2.x which was in Debian
> unstable, and the load-path was /usr/share/emacs/site-lisp/
> but default. When installing this new Emacs the load-path
> was not the same, I did make install and found out that it
> made something in /usr/local/share/emacs/site-lisp/,

This is normal.  By default, Emacs is installed in /usr/local.  This
means binaries go in /usr/local/bin, Lisp files in
/usr/local/share/emacs/VERSION/lisp, and so on.

The Debian package installs in /usr, so the binary goes in /usr/bin
and so on.

Additionally, the Debian packages have added magic so that both Emacs
and XEmacs will find the right Lisp files.  To this end, the *.el
files are stored in the same directory for both Emacs and XEmacs, but
the *.elc files are stored in different directories.  (The *.elc
files are usually incompatible between Emacs flavors.)

> but when I put the programs from the old load-path in that directory
> they didn't load, or work at all.

It's difficult to say what has happened from this description.  Can
you given an example of a "program" that you took from the old
load-path and put it into the new site-lisp directory?

Note that there should be a file site-start.el and/or default.el.
This file contains (these files contain) commands that are necessary
for setting up the add-on packages.  It's not enough to drop a random
*.el file into the right directory, you also have to configure Emacs
to actually use that file.
-- 
file-error; Data: (Opening input file no such file or directory ~/.signature)