Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Expiring old low-score threads
Date: Wed, 17 Apr 2013 22:17:34 +0800	[thread overview]
Message-ID: <87sj2pw8ap.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87r4i9iez8.fsf@thinkpad.tsdh.de>

Tassilo Horn <tsdh@gnu.org> writes:

> Hi all,
>
> I'm reading quite a few high-traffic mailing lists, and my mailbox is
> shortly before running out of space.  So I want to do some expiry.
> Basically, I could use total-expire, say, after 365 days, but I'd prefer
> if I could expire threads I'm not interested in much earlier than
> threads that are interesting to me.
>
> So now I'm trying to write a command that walks over all threads in the
> current summary and marks all threads that have a score lower than -30
> and whose most recent article is older than 60 days as expirable.
> That's what I came up with so far.

[...]

> How can I fix this?  I mean, I obviously want to run my command in
> complete summary containing all articles I've ever received in that
> group.  Of course, chances are high that the group contains incomplete
> threads with false roots where ^ (gnus-summary-refer-parent-article)
> won't cure the symptoms.

It's highly unlikely that I'm actually going to be able to help you with
this, but in trying to write functions that run over *all* the messages
in a group I've usually had to start them like this:

(defun  th-gnus-summary-exprire-old-lowscore-articles (group)
  (interactive (list (gnus-group-group-name)))
  (let ((gnus-large-newsgroup nil))
    (gnus-summary-read-group group t t nil)

That at least ensures that all the available messages are present in the
*Summary* buffer.

To be honest I haven't had much luck manipulating Gnus
programmatically...

Eric





  reply	other threads:[~2013-04-17 14:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17 11:16 Tassilo Horn
2013-04-17 14:17 ` Eric Abrahamsen [this message]
2013-04-17 14:31   ` Tassilo Horn
2013-04-18  0:10     ` Eric Abrahamsen
2013-04-18  6:51       ` Tassilo Horn
2013-04-18  7:08         ` Eric Abrahamsen

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=87sj2pw8ap.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).