Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: total-expire based on msg count
Date: Mon, 22 Mar 2010 14:30:33 -0500	[thread overview]
Message-ID: <87k4t4w3vq.fsf@newsguy.com> (raw)
In-Reply-To: <87634s5c4n.fsf@lifelogs.com>

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Thu, 11 Mar 2010 18:20:28 -0600 Harry Putnam <reader@newsguy.com> wrote: 
>
> HP> I've since converted those groups to nnml, where gnus gets more
> HP> annoyed if I do things behind its back, but it looks like it might be
> HP> harder to get the same result using gnus native functionality.
>
> I think you'll be happier with nnmaildir.  It's designed for sharing and
> Gnus doesn't mind.  So you could have your external script delete
> messages without a Gnus problem.

That may be true... I tried nnmaildir once quite some time ago and
hated the really clunky file names.  If you handle any of it by hand
those names get to be a pain in the butt very soon.






  reply	other threads:[~2010-03-22 19:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-12  0:20 Harry Putnam
2010-03-19 19:45 ` Ted Zlatanov
2010-03-22 19:30   ` Harry Putnam [this message]
2010-03-22 19:43     ` Ted Zlatanov

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=87k4t4w3vq.fsf@newsguy.com \
    --to=reader@newsguy.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).