From: Ted Zlatanov <tzz@lifelogs.com>
To: info-gnus-english@gnu.org
Subject: Re: Gnus registry permanence and spam-log-to-registry
Date: Mon, 22 Mar 2010 08:05:44 -0500 [thread overview]
Message-ID: <87r5nc1p7b.fsf@lifelogs.com> (raw)
In-Reply-To: <87tys8lofy.fsf@nifty.my-fqdn.de>
On Mon, 22 Mar 2010 10:01:53 +0100 "Peter G" <nyhedsgrupper@gmx.com> wrote:
PG> I'm trying to set up the spam.el package in my .gnus.el, so that I'm
PG> going to have simple spam-handling.
PG> My current setup is almost working, save for the simple problem that
PG> everytime I first start up gnus in emacs, I'm being interactively
PG> prompted whether i eant to "enable the gnus registry" and that I have to
PG> look into 'gnus-registry-install' if I want it to be set permanent.
PG> Problem is, I already have set 'gnus-registry-install'. So what am I
PG> missing?
PG> Relevant part of .gnus.el:
PG> (require 'gnus-registry)
PG> (gnus-registry-initialize)
PG> (setq gnus-registry-install t
PG> gnus-registry-max-entries 20000)
It's because of this code in gnus-registry.el:
(when (or (eq gnus-registry-install t)
(gnus-registry-install-p))
(gnus-registry-initialize))
I'll change the docs for the `gnus-registry-install' variable but for
now you should set it before the require or use Customize.
The reason it's a bit annoying like this is that loading the registry
involves hooks and a large data structure. Loading it inadvertently
could slow Gnus down a lot on older machines. Sorry for the
inconvenience.
The rest of your setup looks good. You could use the
(spam-initialize 'backend1 'backend2)
form to enable the backends directly. You don't have to set them before
calling spam-initialize, unlike the gnus-registry initialization.
Ted
next prev parent reply other threads:[~2010-03-22 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 9:01 Peter G
2010-03-22 13:05 ` Ted Zlatanov [this message]
2010-03-22 14:31 ` Ted Zlatanov
2010-03-22 17:50 ` Peter G
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=87r5nc1p7b.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=info-gnus-english@gnu.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).