From: Mark Eichin <eichin@cygnus.com>
Cc: ding@gnus.org
Subject: Re: debugging nnmail-split-fancy
Date: 23 Jul 1997 19:51:37 -0400 [thread overview]
Message-ID: <xe1g1t51g52.fsf@maneki-neko.cygnus.com> (raw)
In-Reply-To: Steinar Bang's message of "22 Jul 1997 08:49:25 +0200"
> But a little more debugging info, would have been nice here.
> Something for the TODO-list, perhaps...?
Well, testing the splits with live mail is unwarrantedly risky -- "B q"
(gnus-summary-respool-query) on a message you've already got is a much
safer test since it doesn't actually *do* anything...
I'm not sure how "Debugging" the splits would actually work,
though... it might be possible to put some optional message calls in
the split handling routines, but they'd have to spew basically
everything ("rule %s didn't match %s" for each rule for each
message...) In case it wasn't clear, the refile to "bogus" is what
happens if it *falls off the end*.
next prev parent reply other threads:[~1997-07-23 23:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-07-22 5:56 Steinar Bang
1997-07-22 6:49 ` Steinar Bang
1997-07-23 17:58 ` Lars Magne Ingebrigtsen
1997-07-23 23:51 ` Mark Eichin [this message]
2019-02-14 8:49 Debugging nnmail-split-fancy Norman Walsh
2019-02-14 15:26 ` Gijs Hillenius
2019-02-14 18:16 ` Andreas Schwab
2019-02-19 17:08 ` Norman Walsh
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=xe1g1t51g52.fsf@maneki-neko.cygnus.com \
--to=eichin@cygnus.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).