Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: spam.el is a bit aggressive loading/saving spam-stat data
Date: Fri, 21 Feb 2003 15:49:56 -0500	[thread overview]
Message-ID: <4nk7ft1hqj.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <y68n0kpv0s7.fsf@multics.mit.edu> (David Z Maze's message of "Fri, 21 Feb 2003 15:25:44 -0500")

On Fri, 21 Feb 2003, dmaze@MIT.EDU wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:

>> How about spam-stat-load on summary entry, and spam-stat-save on
>> summary exit if spam-use-stat is on?
> 
> spam-stat-load needs to be called before splitting happens.  My
> understanding is that, once it's loaded, it doesn't need to be
> reloaded or saved until Emacs exits.

You're right, I was not thinking.

>> That seems like the right place to put those hooks, and you won't
>> have to hit 's' unnecessarily.
> 
> The same code gets called from gnus-group-save-newsrc and
> gnus-group-exit, right?  If spam-stat-save really does need to be
> called often, then calling it on summary exit makes sense, but
> otherwise saving it at the same time as .newsrc.eld would minimize
> (possibly slow) disk access.

Well, it doesn't need to be called often, and it could be added to the
save-newsrc hook.  I just thought most people would want their stats
up-to-date on disk, but I can see why it would be good to minimize
disk access.  Maybe we could allow both behaviors?

What do you think about a new variable spam-stat-save-frequency with
choices "often" and "with-newsrc"?  I guess we don't need "like a
maniac" as an option :)

Ted



  reply	other threads:[~2003-02-21 20:49 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 [this message]
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
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=4nk7ft1hqj.fsf@lockgroove.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).