From: Ted Zlatanov <tzz@lifelogs.com>
Cc: Ding Mailing List <ding@gnus.org>, Dave Love <d.love@dl.ac.uk>
Subject: Re: loading spam.el, spam-stat.el shouldn't install hooks
Date: Fri, 30 May 2003 15:55:00 -0400 [thread overview]
Message-ID: <4n3ciwgqgb.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <rzqaddtsh5b.fsf@albion.dl.ac.uk> (Dave Love's message of "Sun, 11 May 2003 15:16:16 +0100")
The following message is a courtesy copy of an article
that has been posted to gnus.gnus-bug as well.
I modified spam.el, spam-stat.el, and gnus-registry.el to do
conditional loading of their hooks and to have an unload-hook function
available.
For the gnus-registry, you have to set gnus-registry-install.
For spam-stat.el, spam-stat-install-hooks was already in place, so you
probably already have it set if you need it.
For spam.el, spam-install-hooks can be set to t. It will be nil by
default unless the user has set one of the spam-use-* variables to t,
e.g. spam-use-bogofilter or spam-use-stat.
Dave, if you could check on this to make sure I am doing the right
thing, I'd appreciate it.
Ted
parent reply other threads:[~2003-05-30 19:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <rzqaddtsh5b.fsf@albion.dl.ac.uk>]
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=4n3ciwgqgb.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=d.love@dl.ac.uk \
--cc=ding@gnus.org \
/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).