From: Ole Andre Birkedal <oandre-b@online.no>
Subject: Re: Emacs load-path after update
Date: 13 Apr 2003 01:19:14 +0200 [thread overview]
Message-ID: <87ptnr483x.fsf@online.no> (raw)
In-Reply-To: 848yufviqn.fsf@lucy.is.informatik.uni-duisburg.de
kai.grossjohann@gmx.net (Kai Großjohann) writes:
> 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?
Yes, there was very little detail about that, let me try to fill
in on that, sorry.
I am running gnus with mailcrypt just fine in the cvs compiled version
of Emacs, probably because it came with it. When I installed it, it
put gnus and mailcrypt in /usr/local/share/emacs/21.3.50/lisp, as you said.
The program I am trying to move is ERC, the IRC client for Emacs.
I have tried moving it into /usr/local/share/emacs/21.3.50/lisp, as well
as /usr/local/share/emacs/site-lisp/ with no luck.
> Note that there should be a file site-start.el and/or default.el.
Yes, I was thinking about this, since I have never (AFAIK) had any of
these files for ERC. But I looked around a bit, and there is a mailcrypt-init.el
in /usr/local/share/emacs/site-lisp/, maybe that could explain something?
> 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)
As I am not a very experienced Emacs user I can't fill in on very much more than
that. I don't know what more to tell you really, sorry. Hoper it was enough info anyway.
In advance, thanks. :-)
--
the Termos, Ole André
http://termos.devcave.net
next prev parent reply other threads:[~2003-04-12 23:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-12 15:13 Emacs load-path after update Ole Andre Birkedal
2003-04-12 15:27 ` Kai Großjohann
2003-04-12 23:19 ` Ole Andre Birkedal [this message]
2003-04-13 8:02 ` Kai Großjohann
2003-04-13 8:34 ` Ole Andre Birkedal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ptnr483x.fsf@online.no \
--to=oandre-b@online.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).