Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@iskon.hr>
Subject: Re: Expire by moving
Date: 20 Apr 2000 13:23:45 +0200	[thread overview]
Message-ID: <dpn1mpow1q.fsf@mraz.iskon.hr> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "20 Apr 2000 02:49:41 +0200"

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Hrvoje Niksic <hniksic@iskon.hr> writes:
> 
> > > So I thought that it would be nice if gnus had a feature to expire
> > > messages not by /deleting/ them, but by /moving/ them to some
> > > arbitrary group.
> > 
> > That would rule.  When we were in Japan, Lars agreed that it would be
> > totally cool, and said he'd implement it.
> > 
> > Laaaaaaaaaaaaaaaaaaaaaars!
> 
> Er, so I did.
> 
> So, how should this be specified?  Moved to which group, etc?

The existing `expire' stuff should remain untouched (types, periods,
etc.), all one should need to add is some sort of "target" of the
expiration.

The default expire-target target is simply `delete', while I can
imagine this addition would add a `move' target (`copy' wouldn't make
much sense).  For instance, you could use this as group parameters for
a "private" group where private mail lands:

((total-expire . t)
 (expiry-wait . 28)    ; keep a month old mails around
 (expiry-target . "nnfolder:really-old-private"))

The expiry-target parameter could also be a form that specifies the
group dynamically, so you can do the file-per-month trick described
under archive section.



  parent reply	other threads:[~2000-04-20 11:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-01 17:38 Arcady Genkin
2000-04-01 19:28 ` Kai Großjohann
2000-04-02  7:44   ` Arcady Genkin
2000-04-03  7:39     ` Kai Großjohann
2000-04-05  7:56     ` Alf-Ivar Holm
2000-04-03  2:33 ` Andrew Hobson
2000-04-03  7:15 ` Hrvoje Niksic
2000-04-20  0:49   ` Lars Magne Ingebrigtsen
2000-04-20  1:05     ` Daniel Pittman
2000-04-20 11:23     ` Hrvoje Niksic [this message]
2000-04-20 12:59       ` Lars Magne Ingebrigtsen
2000-05-02  8:35     ` Arcady Genkin

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=dpn1mpow1q.fsf@mraz.iskon.hr \
    --to=hniksic@iskon.hr \
    /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).