From: Jack Vinson <jvinson@chevax.ecs.umass.edu>
Subject: nested requests (gnus + bbdb 2.0)
Date: 19 Nov 1998 10:02:09 -0600 [thread overview]
Message-ID: <wkaf1nr7r2.fsf@chevax.ecs.umass.edu> (raw)
I probably made a mistake upgrading to emacs 20.3, pgnus AND bbdb 2.0 all
in the same day, but everything seems to be working.
I thought emacs knew how to handle these things, but there are looped
require dependencies between gnus and bbdb that cause emacs to error with
an infinite loop of package loading.
Since the problem starts on the load of message (specifically, when it runs
the message-load-hooks), I simply swapped the (provide 'message) and
(run-hooks 'message-load-hooks) lines.
Is there a better way to take care of this problem generically? Should
bbdb have (require 'gnus) embedded in the file that gets autoloaded by a
function in my message-load-hook?
--
Jack Vinson <jvinson@chevax.ecs.umass.edu> http://www.cis.upenn.edu/~vinson/
Zippy: I am KING BOMBA of Sicily!..I will marry LUCILLE BALL next Friday!
next reply other threads:[~1998-11-19 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-19 16:02 Jack Vinson [this message]
1998-11-19 16:37 ` Jan Vroonhof
1998-11-19 16:59 ` Colin Rafferty
1998-11-20 2:38 ` Lars Magne Ingebrigtsen
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=wkaf1nr7r2.fsf@chevax.ecs.umass.edu \
--to=jvinson@chevax.ecs.umass.edu \
/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).