Gnus development mailing list
 help / color / mirror / Atom feed
From: Mark Eichin <eichin@cygnus.com>
Subject: switching to nnmail-split-fancy (summary: *read* the documentation :-)
Date: 18 May 1996 22:06:33 -0400	[thread overview]
Message-ID: <xe1g28xfmc6.fsf_-_@maneki-neko.cygnus.com> (raw)
In-Reply-To: Steven L Baur's message of 18 May 1996 16:13:12 -0700

Just thought I'd share some mistakes I made switching from a
nnmail-split-methods list to nnmail-split-fancy. I have a *large*
split list (over 90 elements). The first step was to use

      (mapcar (lambda (x) (list 'any (car (cdr x)) (car x)))
             nnmail-split-methods))

to turn it into a list of (any "pattern" "mailbox") entries, and wrap
that in an '(| ...) group.

First mistake: (any "" "mail.misc") does *not* catch everything that
falls off the end. If the pattern matches nothing (which is *not* the
same as getting a lisp error -- that's handled, and drops things in
nnml:bogus) the mail is *not sorted* and goes nowhere. First fix is to
change that entry to a simple "mail.misc" which gets everything
without trying to match.

Second mistake: the page on Fancy Splitting *very clearly* states that
the "field contents" part of a match is matched as a *word*. It wasn't
until I was deeply single-stepped into nnmail-split-it that I noticed
the use of \\< and \\>, and went back to the docs, and saw it... Ohh,
he said *word*, he really meant *word*. (oops.) So, a bunch of rules
got ".*" added to the end (close enough for now, a few of them could
be pruned in other ways.)

After all that (and Respooling two days worth of Incoming* files after
discovering that half of my mail was falling out the bottom and not
getting filtered at all... yay for nnmail-delete-incoming defaulting
to nil :-)) and tweaking a few rules that used to match whole lines
into matching field and content seperately, I'm pretty happy with it.

Suggestion: it might be nice to add '(dest . "to\\|cc\\|apparently-to")
to nnmail-split-abbrev-alist. I happen to use it particularly to
distinguish between mail from me and mail to me, but it's also useful
for some of the netbsd lists (source-changes, in particular, comes
from owner-current-users, and would get sorted wrong using 'any.)

Ok, enough of that, thanks for listening, thanks for gnus! (It is just
amazing how much time gnus saves me, even when I don't configure it to
throw away all of my mail :-)
					_Mark_ <eichin@cygnus.com>
					Cygnus Support, Eastern USA




             reply	other threads:[~1996-05-19  2:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-05-19  2:06 Mark Eichin [this message]
1996-05-19 22:37 ` Per Abrahamsen

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=xe1g28xfmc6.fsf_-_@maneki-neko.cygnus.com \
    --to=eichin@cygnus.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).