Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Cc: Oystein Viggen <oysteivi@tihlde.org>, ding@gnus.org
Subject: Re: periodic archiving of groups?
Date: 22 Jan 2001 13:03:39 -0800	[thread overview]
Message-ID: <m3u26rwb84.fsf@reader.newsguy.com> (raw)
In-Reply-To: Rob Browning's message of "22 Jan 2001 13:28:05 -0600"

Rob Browning <rlb@cs.utexas.edu> writes:

> I wouldn't mind having to do this manually, though it'd be really nice
> to have an automated way to handle it.
> 
> I might be interested in writing the elisp for this if someone could
> get me pointed in the right direction (I'd want to base the splitting
> on the actual message date, not the article numbers...)

The elisp for most of it is already written.  You seem to be talking
of nnml groups here (judging from previous post).  You can do this by
writing a separtate set of split rules and keeping them in a separate
file.  When you want to do this archiving you would load that file
which would override the split in .gnus.  Then enter the subject
group with C-u <RET> mark all but the last mnths messages by using the
limit `/ t' features then respool them according to your newly loaded
rules.

The new rules will look like:
(setq nnmail-split-methods 
  '(("SOMEGROUP_FEB-00" "^Date:.*Feb.*2000") 
     ("SOMEGROUP_MAR-00" "^Date:.*Mar.*2000")
etc etc
When done have gnus reread ~/.gnus or restart, to reload the original
split urules then back to business as usual.

You'll probably need to run `nnml-generate-nov-databases' since some
groups will have been severely truncated.  


etc etc



  reply	other threads:[~2001-01-22 21:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-19  0:20 Anil B. Somayaji
2001-01-19  0:32 ` ShengHuo ZHU
2001-01-19  1:48   ` Small user interface patch to gpg.el Colin Marquardt
2001-01-19  2:04     ` ShengHuo ZHU
2001-01-19  2:54     ` Agh! X-Draft-From: header! (was: Small user interface patch to gpg.el) Colin Marquardt
2001-01-19 12:18       ` Kai Großjohann
2001-01-19 12:37         ` Karl Kleinpaste
2001-01-19 13:13           ` Kai Großjohann
2001-01-19 18:07             ` Colin Marquardt
2001-01-19 17:40               ` Simon Josefsson
2001-01-19 19:43               ` S/MIME buttons Colin Marquardt
2001-01-20  0:05                 ` Simon Josefsson
2001-01-20  0:15                   ` ShengHuo ZHU
2001-01-20  0:40                   ` Colin Marquardt
2001-01-19  3:56   ` periodic archiving of groups? Alan Shutko
2001-01-19  4:07     ` Alan Shutko
2001-01-19 10:26       ` Oystein Viggen
2001-01-19 14:32         ` Alan Shutko
2001-01-19 16:53           ` Oystein Viggen
2001-01-19 17:42             ` Alan Shutko
2001-01-22 19:28         ` Rob Browning
2001-01-22 21:03           ` Harry Putnam [this message]
2001-01-19 12:16 ` Kai Großjohann
2001-01-22 19:24   ` Rob Browning

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=m3u26rwb84.fsf@reader.newsguy.com \
    --to=reader@newsguy.com \
    --cc=ding@gnus.org \
    --cc=oysteivi@tihlde.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).