From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: bug/feature?: gnus-data-list is not ready in
Date: Fri, 09 Jan 2004 16:41:58 -0500 [thread overview]
Message-ID: <4nu134ol3t.fsf@collins.bwh.harvard.edu> (raw)
In-Reply-To: <4nk741otcx.fsf_-_@collins.bwh.harvard.edu> (Ted Zlatanov's message of "Fri, 09 Jan 2004 13:43:42 -0500")
On Fri, 09 Jan 2004, tzz@lifelogs.com wrote:
> Hmm, now I got the error in other news servers. I think the
> gnus-data-list function is not ready to give me valid data in the
> gnus-summary-prepare hook. Can anyone tell me how I can circumvent
> this?
Bah, it was so simple I never thought of it. gnus-newsgroup-data is
buffer-local to the gnus-summary-buffer. I was doing my insertion in
a (with-temp-buffer) form, so debugging was showing me everything was
fine but when I ran things they didn't work. Incidentally,
(with-current-buffer) inside a (with-temp-buffer) form does not do
the right thing with regards to buffer-local variables. I'm fighting
the urge to spell "buffer" as "bugger" :)
Sorry for the trouble. Fix is in CVS - the latest spam.el should be
much, much faster at autodetecting articles when using non-statistical
backends such as spam-use-BBDB. It will still request the complete
article if a backend that uses statistics or extra headers needs it,
such as spam-use-bogofilter, but when possible a "fake" article will
be built instead from the overview data, and the backend function
will be run on that. The speedup is tremendous - spam-autodetect is
finally, I think, fast enough for regular usage.
Ted
prev parent reply other threads:[~2004-01-09 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 22:51 (gnus-data-list nil) does not give valid data sometimes Ted Zlatanov
2004-01-09 0:58 ` Ted Zlatanov
2004-01-09 18:43 ` bug/feature?: gnus-data-list is not ready in gnus-summary-prepare-hook (was: (gnus-data-list nil) does not give valid data sometimes) Ted Zlatanov
2004-01-09 21:41 ` Ted Zlatanov [this message]
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=4nu134ol3t.fsf@collins.bwh.harvard.edu \
--to=tzz@lifelogs.com \
/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).