Gnus development mailing list
 help / color / mirror / Atom feed
From: Andreas Fuchs <asf@void.at>
Subject: Re: Autoloads no longer working?
Date: Thu, 25 Apr 2002 12:24:04 +0200	[thread overview]
Message-ID: <E170gQ0-0000rg-00@eris.void.at> (raw)
In-Reply-To: <vafpu0pneja.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>

On 2002-04-24, Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE>
wrote:
> Andreas Fuchs <asf@void.at> writes:
> 
>> I add the path as soon as possible; Even when I start emacs with -q,
>> the features are present. Could that be a debian emacs bug?
> 
> Ayee.  I think Debian has /etc/emacs/site-start.d which contains
> files which might load Gnus.

Tested it:

emacs -q -no-site-file # doesn't have gnus loaded

emacs -q -no-site-file # with (debian-startup 'emacs21) evaluated
                       # doesn't have gnus loaded

emacs -q -no-site-file # with (debian-startup 'emacs) evaluated
                       # doesn't have gnus loaded, either!

emacs -q               # has gnus loaded.

This is very strange, and I have no idea where this sucker could be
loaded. My only choice is removing the gnus directory in my emacs lisp
installation and trying to find out where the backtrace appears. (-:

> Hm.
> 
> You could frob the files in that directory (add `message' statements)
> to find out which one leads to Gnus being loaded.  Then you can
> follow that trail.
> 
> You know, Gnus has to be loaded _somewhere_.

I know. And that's what is confusing me.. somewhere along that path,
gnus gets loaded, but I have no idea where.

Thanks for your help,
-- 
Andreas Fuchs, <asf@acm.org>, asf@jabber.at, antifuchs



  reply	other threads:[~2002-04-25 10:24 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 [this message]
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
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=E170gQ0-0000rg-00@eris.void.at \
    --to=asf@void.at \
    /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).