Gnus development mailing list
 help / color / mirror / Atom feed
From: George McNinch <gmcninch@gmail.com>
To: ding@gnus.org
Subject: more verbose expiry?
Date: Tue, 28 Jun 2011 15:42:50 -0400	[thread overview]
Message-ID: <87sjqtlp39.fsf@gmail.com> (raw)

Is it possible for the expiry process to give more details?

I have populated

nnmail-fancy-expiry-targets

so that when I "E" articles e.g. in my gmail INBOX and then expire the
group, some of those marked E go to the trash, while others go
(hopefully) to more appropriate destinations (for example, any mail
to-from my wife goes to a particular folder). So I use expiry for
archiving.

For the most part, this works fine for me.

But the report given in the *Messages* buffer is not useful for tracking
down any misconfigurations; e.g. this is typical:

Expiring articles...
Expiring article INBOX:19736
Expiring article INBOX:19737
Expiring article INBOX:19741
Expiring articles...done

I wonder how hard it would be to have those *Messages* say more?  Could
they indicate for each article what the outcome of the expiration
process was (i.e. the destination folder)?  And maybe give more
human-identifiable info about the expired articles than their numbers?

(Or maybe this is already possible and I've overlooked some
configuration option...?)

-- 
George McNinch <gmcninch(at)gmail.com>
http://gmcninch.math.tufts.edu




             reply	other threads:[~2011-06-28 19:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28 19:42 George McNinch [this message]
2011-06-30  2:43 ` Lars Magne Ingebrigtsen
2011-06-30 11:23   ` George McNinch
2011-07-02 14:11   ` Dave Abrahams
2011-07-02 14:16     ` Lars Magne Ingebrigtsen

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=87sjqtlp39.fsf@gmail.com \
    --to=gmcninch@gmail.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).