Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Re: many articles
Date: 19 Sep 1998 20:55:43 -700	[thread overview]
Message-ID: <m3sohnxwsg.fsf@chub.local> (raw)
In-Reply-To: Phil Humpherys's message of "19 Sep 1998 21:05:11 -0600"

Phil Humpherys <phumpherys@utah-inter.net> writes:

> Well, this may be an option down the road, but for now it simply
> isn't.  Instead, I'm going to have to modify how I interact with
> my email somewhat.  I'm dedicated to staying with gnus, but I'm
> going to have make it work with mh as I've described above.
> 
> Thanks again for your response.  I'd appreciate any further help
> or suggestions.
Another course would be to break the monster groups down by mnth or
whatever into several nnml groups.

Or you could setup a tempory split to split them into nnfolder groups
quite quickly.  This *should* generate the groups named in the split.  

Something like this should do it.  Evaluate the temp split, then enter
the group and process mark every thing you want split out (From the
top of summary buffer do C-u 11,000 `#' or whatever number) Then press 
`B r' (respool) and choose `nnfolder' as the backend to do the
respooling.  Then step back and watch it fly...

(beware untested)
;;temp split
(setq nnmail-split-methods
      '(("group-mnth1" "^Date:.*Jan.*1997")
          ("group-mnth2" "^Date:.*Feb.*1997")
          ("group-mnth3" "Date.*Mar.*1997")
            ("group-mnth4" "^Date:.*Apr.*1997")))

etc etc

-- 
Harry Putnam reader@newsguy.com  
Running Redhat Linux-5.1


  reply	other threads:[~1998-09-20  3:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-19 18:50 Phil Humpherys
1998-09-19 20:49 ` Matt Simmons
1998-09-20  3:05   ` Phil Humpherys
1998-09-20  3:55     ` Harry Putnam [this message]
1998-09-20 20:26     ` Kai Grossjohann
1998-09-21  2:12       ` Matt Simmons
1998-09-21  3:33         ` Phil Humpherys
1998-09-21  8:01           ` Kai Grossjohann

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=m3sohnxwsg.fsf@chub.local \
    --to=reader@newsguy.com \
    /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).