Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: spam.el is a bit aggressive loading/saving spam-stat data
Date: Sat, 01 Mar 2003 10:08:00 -0500	[thread overview]
Message-ID: <m3r89rktv3.fsf@heechee.beld.net> (raw)
In-Reply-To: <y68fzq7tdy5.fsf@multics.mit.edu> (David Z Maze's message of "Sat, 01 Mar 2003 08:26:58 -0500")

On Sat, 01 Mar 2003, dmaze@MIT.EDU wrote:
> Well, the good news: Gnus no longer takes multiple seconds per
> message to read mail.  :-) The bad news, part 1, is that this only
> works if spam-use-stat is defined before spam.el is loaded.  (So if
> you (require 'spam) at the top of your .gnus, say, you lose.)  This
> patch fixes that:

I added the patch, but modified it for style (I prefer when to if for
single logicals), I hope you don't mind :)

> Even with that, spam-stat-load doesn't seem to get called when Gnus
> is loaded.  What in gnus-1 causes incoming mail to be read on
> startup?  The only call to gnus-group-get-new-news there is
> protected by a call to gnus-alive-p, and the code seems to leap from
> reading in all of the prerequisite files to building the group
> buffer.  Does something in the startup sequence actually run
> gnus-get-new-news-hook?

I added 

      (add-hook 'gnus-startup-hook 'spam-maybe-spam-stat-load))

to the list of hook modifications, since loading the stats twice
shouldn't hurt and it seems like the safest way to force the loading.
Let me know if it works.

I don't know why gnus-1 is not calling the stats loading, sorry.

Ted




  reply	other threads:[~2003-03-01 15:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 18:22 David Z Maze
2003-02-21  8:16 ` Niklas Morberg
2003-02-21 15:14 ` Ted Zlatanov
2003-02-21 20:25   ` David Z Maze
2003-02-21 20:49     ` Ted Zlatanov
2003-02-21 21:06       ` David Z Maze
2003-02-21 23:58       ` Alex Schroeder
2003-02-24 21:53         ` Ted Zlatanov
2003-02-26  2:23           ` David Z Maze
2003-02-26 21:15             ` Ted Zlatanov
2003-03-01 13:26               ` David Z Maze
2003-03-01 15:08                 ` Ted Zlatanov [this message]
2003-03-02 23:49                   ` David Z Maze
2003-03-06 13:22                     ` Niklas Morberg
2003-03-06 15:39                       ` Ted Zlatanov
2003-03-07 14:27                         ` Bill White
2003-03-07 14:38                           ` Niklas Morberg
2003-03-07 15:13                             ` Bill White
2003-03-10  8:05                               ` Niklas Morberg
2003-03-11 12:53                                 ` Bill White
2003-03-07 14:55                           ` Ted Zlatanov
2003-03-07 22:55                             ` A.J. Rossini
2003-03-08  0:49                               ` Alex Schroeder

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=m3r89rktv3.fsf@heechee.beld.net \
    --to=tzz@lifelogs.com \
    --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).