From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: adaptive expiry? feature request?
Date: Thu, 01 Aug 2013 18:44:22 +0200 [thread overview]
Message-ID: <m3haf98iop.fsf@stories.gnus.org> (raw)
In-Reply-To: <87zjyqsys3.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Tue, 26 Feb 2013 18:41:48 +0000")
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> What I would like is to have an expiry policy that is adaptive, in the
> same way as scoring is. In fact, I would love to have an expiry time
> that is a function of the score (meaning that active threads, for
> instance, would not expire for quite a long time) and I guess other
> message attributes. In other words, a more general version of the
> nnmail-expiry-wait-function and nnmail-fancy-expiry-targets functions
> would be quite nice to have!
>
> Is such a thing possible? I've searched gnus variables and done a web
> search of sorts but found nothing. I think it should be possible (maybe
> even straightforward?) to implement but my elisp is not good enough to
> even think about doing this.
I don't think there's anything in Gnus for doing that fine-grained
expiry, unfortunately.
If you look at (for instance) `nnml-request-expire-articles' (or
whatever mail backend you use), `nnmail-expired-article-p' is called to
determine whether an article is "old". You'd have to wrap that call
with something that sets nnmail-expiry-wait with something that depends
on the score of the article.
> Footnotes:
> [1] does any other MUA have scoring? Not that I intend to change :-)
> Just curious.
At the time Gnus introduced scoring (1993?) there were definitely a lot
of discussion about how to deal with the amazingly huge information
overload from Usenet. >"? So I don't think the scoring idea was
original to Gnus. I think we developed the adaptive scoring thing at
Gnus, though.
--
(domestic pets only, the antidote for overdose, milk.)
No Gnus T-Shirt for sale: http://ingebrigtsen.no/no.php
next prev parent reply other threads:[~2013-08-01 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 18:41 Eric S Fraga
2013-06-06 15:45 ` Ted Zlatanov
2013-08-01 16:44 ` Lars Magne Ingebrigtsen [this message]
2013-09-04 15:47 ` Eric S Fraga
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=m3haf98iop.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--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).