From: Ted Zlatanov <tzz@lifelogs.com>
To: Norman Walsh <ndw@nwalsh.com>
Cc: ding@gnus.org
Subject: Re: split-fancy and gnus-registry confusion
Date: Wed, 05 Mar 2008 13:05:39 -0600 [thread overview]
Message-ID: <86tzjl6lfg.fsf@lifelogs.com> (raw)
In-Reply-To: <m2mypd1fva.fsf@nwalsh.com> (Norman Walsh's message of "Wed, 05 Mar 2008 08:04:41 -0500")
On Wed, 05 Mar 2008 08:04:41 -0500 Norman Walsh <ndw@nwalsh.com> wrote:
NW> / Norman Walsh <ndw@nwalsh.com> was heard to say:
NW> | I have no idea how/why it traced <m23ar738ty.fsf@nwalsh.com> to nnml:misc.
NW> | It isn't there, it wasn't sent from there, and it's never been there. Here
NW> | are the headers for it:
NW> [...]
NW> | Curiously, if I look in .gnus.registry.eld, sure enough I find:
NW> |
NW> | ("<m23ar738ty.fsf@nwalsh.com>" ((mtime 18380 22548 203572)) "w3c.member.tag" "nnml:misc")
NW> |
NW> | So now I guess the question is, who decided to put nnml:misc in there?
NW> And the answer to that question is, because this split rule didn't match:
NW> ("sender" "^tag-request@w3.org" "w3c.member.tag")
NW> I took the "^" out, moved it down a little bit in the list, and now the
NW> right thing happens. And I think this resolves the mystery of how *my
NW> original* got misfiled. And that, in turn, resolves the mystery of why
NW> the parents were wrong.
NW> So it was user error after all. But we knew that already, right? :-)
It was good that the debugging info helped you. Because the registry is
so thorough about catching articles, these problems will happen so I'm
glad new users of the registry will not suffer like you and Jake Colman
did :)
Ted
next prev parent reply other threads:[~2008-03-05 19:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 17:09 Norman Walsh
2008-02-27 22:40 ` Ted Zlatanov
2008-02-28 14:09 ` Jake Colman
2008-02-28 14:32 ` Ted Zlatanov
2008-02-28 14:36 ` gnus-registry logging and splitting improvements (was: split-fancy and gnus-registry confusion) Ted Zlatanov
2008-02-28 14:38 ` split-fancy and gnus-registry confusion Ted Zlatanov
2008-03-03 16:07 ` Norman Walsh
2008-03-03 21:23 ` Ted Zlatanov
2008-03-04 17:14 ` Norman Walsh
2008-03-04 17:19 ` Ted Zlatanov
2008-03-04 21:14 ` Norman Walsh
2008-03-04 21:24 ` Ted Zlatanov
2008-03-05 12:49 ` Norman Walsh
2008-03-05 13:04 ` Norman Walsh
2008-03-05 19:05 ` Ted Zlatanov [this message]
2008-03-05 19:03 ` Ted Zlatanov
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=86tzjl6lfg.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=ndw@nwalsh.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).