Gnus development mailing list
 help / color / mirror / Atom feed
From: Norman Walsh <ndw@nwalsh.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: split-fancy and gnus-registry confusion
Date: Wed, 05 Mar 2008 08:04:41 -0500	[thread overview]
Message-ID: <m2mypd1fva.fsf@nwalsh.com> (raw)
In-Reply-To: <m2ir01pc7z.fsf@nwalsh.com> (Norman Walsh's message of "Wed, 05 Mar 2008 07:49:36 -0500")

[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]

/ Norman Walsh <ndw@nwalsh.com> was heard to say:
| I have no idea how/why it traced <m23ar738ty.fsf@nwalsh.com> to nnml:misc.
| It isn't there, it wasn't sent from there, and it's never been there. Here
| are the headers for it:
[...]
| Curiously, if I look in .gnus.registry.eld, sure enough I find:
|
| ("<m23ar738ty.fsf@nwalsh.com>" ((mtime 18380 22548 203572)) "w3c.member.tag" "nnml:misc")
|
| So now I guess the question is, who decided to put nnml:misc in there?

And the answer to that question is, because this split rule didn't match:

  ("sender" "^tag-request@w3.org" "w3c.member.tag")

I took the "^" out, moved it down a little bit in the list, and now the
right thing happens. And I think this resolves the mystery of how *my
original* got misfiled. And that, in turn, resolves the mystery of why
the parents were wrong.

So it was user error after all. But we knew that already, right? :-)

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | There has never been a perfect
http://nwalsh.com/            | government, because men have passions;
                              | and if they did not have passions,
                              | there would be no need for
                              | government.-- Voltaire

[-- Attachment #2: Type: application/pgp-signature, Size: 185 bytes --]

  reply	other threads:[~2008-03-05 13:04 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 [this message]
2008-03-05 19:05                   ` Ted Zlatanov
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=m2mypd1fva.fsf@nwalsh.com \
    --to=ndw@nwalsh.com \
    --cc=ding@gnus.org \
    --cc=tzz@lifelogs.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).