Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Autoloads no longer working?
Date: Fri, 26 Apr 2002 11:48:52 +0200	[thread overview]
Message-ID: <vafu1pysscb.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <E1710pp-0006e2-00@eris.void.at> (Andreas Fuchs's message of "Fri, 26 Apr 2002 10:12:05 +0200")

Andreas Fuchs <asf@void.at> writes:

> On 2002-04-25, Manoj Srivastava <srivasta@acm.org> wrote:
>> 	The file you are thinking about is installed by the standalone
>>  gnus package in Debian, and not by the various flavours of emacsen.
>> 
>> 	Specifically, the file is
>> 	/etc/emacs20/site-start.d/20gnus-init.el.
>>  It is not installed for emacs21. And when it is run for emacs20, the
>>  first thing it does to put the file path for the standalone gnus at
>>  the beginning of the load path.
>
> Strange, in my emacs installation, there is a
> /usr/share/emacs21/lisp/gnus directory, which even contains files. It
> seems like gnus-start from there gets loaded.

We were talking about /etc/emacs*/site-start.d, not
/usr/share/emacs21/lisp/gnus...

Here's a way to find out what's happening:

* delete gnus-start.elc (actually, just rename it)
* put (debug) near the beginning of the file gnus-start.el

Then start Emacs.  You should get a backtrace.  From this backtrace,
it should be possible to see which code loads it.

Also, you can put (message "foo") statements in various places in the
site-wide init files to see what's happening.

kai
-- 
Silence is foo!



  reply	other threads:[~2002-04-26  9:48 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23 10:05 Andreas Fuchs
2002-04-23 13:43 ` Kai Großjohann
2002-04-23 15:04   ` Andreas Fuchs
2002-04-23 15:29     ` Kai Großjohann
2002-04-24 15:54       ` Andreas Fuchs
2002-04-24 16:08         ` Paul Jarc
2002-04-24 18:21         ` Kai Großjohann
2002-04-25 10:24           ` Andreas Fuchs
2002-04-26  3:01           ` Manoj Srivastava
2002-04-26  8:11             ` Andreas Fuchs
2002-04-26  9:57               ` Manoj Srivastava
2002-04-26 13:00                 ` Andreas Fuchs
2002-04-26 13:32                   ` Kai Großjohann
2002-04-26 13:56                     ` Andreas Fuchs
2002-04-26 15:01                       ` Kai Großjohann
2002-04-26 16:53                         ` Andreas Fuchs
2002-04-26 18:22                           ` Kai Großjohann
2002-04-27 16:14                             ` Andreas Fuchs
2002-04-26 17:11                         ` Harry Putnam
2002-04-27 22:59                     ` Paul Jarc
2002-04-28 12:07                       ` Kai Großjohann
2002-04-28 17:43                       ` Paul Jarc
2002-04-26  8:12             ` Andreas Fuchs
2002-04-26  9:48               ` Kai Großjohann [this message]
2002-04-26  8:23             ` Kai Großjohann
2002-04-26  9:32               ` Manoj Srivastava
2002-04-30 15:58     ` amos+lists.ding
2002-04-30 19:45       ` Amos Gouaux
2002-05-05 15:22       ` Amos Gouaux
2002-05-05 15:39         ` Kai Großjohann
2002-05-05 21:45           ` Amos Gouaux

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vafu1pysscb.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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 NNTP newsgroup(s).