From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: <ding@gnus.org>
Subject: adaptive expiry? feature request?
Date: Tue, 26 Feb 2013 18:41:48 +0000 [thread overview]
Message-ID: <87zjyqsys3.fsf@ucl.ac.uk> (raw)
Hello,
I used to use splitting to move all of my incoming email to various
groups. Each group would then have different expiration policies (and
targets). However, I hated having to switch between groups so I moved
to using scoring instead and having many of my emails (non-list ones,
say) sit in one group. Scoring (even non-adaptive) is brilliant [1] and
I would have a hard time not using it any more!
However, this means that all of these emails are expired using the same
policy.
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.
Thanks,
eric
Footnotes:
[1] does any other MUA have scoring? Not that I intend to change :-)
Just curious.
--
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 + Ma Gnus v0.6 + evil 1.0-dev
: BBDB version 3.02 ($Date: 2013/02/16 14:37:17 $)
next reply other threads:[~2013-02-26 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 18:41 Eric S Fraga [this message]
2013-06-06 15:45 ` Ted Zlatanov
2013-08-01 16:44 ` Lars Magne Ingebrigtsen
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=87zjyqsys3.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).