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:03:55 -0600 [thread overview]
Message-ID: <86y78x6lic.fsf@lifelogs.com> (raw)
In-Reply-To: <m2ir01pc7z.fsf@nwalsh.com> (Norman Walsh's message of "Wed, 05 Mar 2008 07:49:36 -0500")
On Wed, 05 Mar 2008 07:49:36 -0500 Norman Walsh <ndw@nwalsh.com> wrote:
NW> That did it. I wonder where gnus-verbose is getting reset? I set it in
NW> *scratch* and it *seemed* persistent. Anyway...
I don't know, sorry.
NW> Here's what I get for one of the misfiled messages:
NW> gnus-registry-split-fancy-with-parent is looking for matches for reference <m23ar738ty.fsf@nwalsh.com> from [ <m23ar738ty.fsf@nwalsh.com>]
NW> gnus-registry-split-fancy-with-parent traced the reference <m23ar738ty.fsf@nwalsh.com> from [ <m23ar738ty.fsf@nwalsh.com>] to group nnml:misc
NW> gnus-registry-split-fancy-with-parent traced the reference <m23ar738ty.fsf@nwalsh.com> from [ <m23ar738ty.fsf@nwalsh.com>] to group w3c.member.tag
NW> gnus-registry-post-process-group: too many extra matches ((misc w3c.member.tag)) for references <m23ar738ty.fsf@nwalsh.com>. Returning none.
NW> nil
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> Curiously, if I look in .gnus.registry.eld, sure enough I find:
NW> ("<m23ar738ty.fsf@nwalsh.com>" ((mtime 18380 22548 203572)) "w3c.member.tag" "nnml:misc")
NW> So now I guess the question is, who decided to put nnml:misc in there?
It was the registry. It hooks into each backend's functionality (spool,
move, copy) and also notices new articles in every group you visit. I
don't know how and when this happened, though.
As I mentioned in another message, I think giving up on multiple matches
is not ideal. We can do better. Maybe the registry could ask the user
in such cases for the right strategy?
Ted
prev parent reply other threads:[~2008-03-05 19:03 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
2008-03-05 19:03 ` Ted Zlatanov [this message]
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=86y78x6lic.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).