split-fancy and gnus-registry confusion

split-fancy and gnus-registry confusion

[Norman Walsh]

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

I'm completely confused by something.

I'm using nnmail-split-fancy and gnus-registry-split-fancy-with-parent:

(require 'gnus-registry)

(setq gnus-registry-max-entries 5000
      gnus-registry-use-long-group-names t)

(setq nnmail-split-fancy-with-parent-ignore-groups
      '("spam.missed"
	"archive\\..*"))

(gnus-registry-initialize)

(setq nnmail-split-fancy
      '(|    ("X-DSPAM-Result" "Spam" "spam.caught")
       (|    ("X-SPAM-Charset" "yes.*" "spam.missed")
       (& (| (: gnus-registry-split-fancy-with-parent)
	     ("sender" "ubuntu-announce.*@lists\.ubuntu\.com" "ubuntu.announce")
	     ("sender" "ubuntu-users.*@lists\.ubuntu\.com" "ubuntu.users")
             ...)))))

I have a message:

  From: Norman Walsh <ndw@nwalsh.com>
  To: tag@w3.org
  Subject: XML 2.0
  X-Draft-From: ("w3c.member.tag")
  BCC: normanwalsh+bcc@gmail.com
  X-URL: http://nwalsh.com/
  X-Countdown: T-minus 47 weeks, 5 days, 17 hours, 2 minutes, 42 seconds
  Date: Wed, 20 Feb 2008 13:58:25 -0500
  Message-ID: <m2wsozqwtq.fsf@nwalsh.com>
  User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1.50 (darwin)
  MIME-Version: 1.0
  Content-Type: multipart/signed; boundary="=-=-=";
  	micalg=pgp-sha1; protocol="application/pgp-signature"
  Lines: 28
  Xref: nwalsh.com w3c.member.tag:6082

  ...

If I put the cursor in that message and run 
(gnus-registry-split-fancy-with-parent), it returns "nil", as I'd expect.

But if I do B t, I get:

(: gnus-registry-split-fancy-with-parent)
"misc"
(: nwalsh-incoming-group)
"archive.2008-02"

which I find totally baffling. Where is that 'misc' coming from?

Note that gnus-registry-track-extra is nil.

Any clues you can provide would be most helpful.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | When it is not necessary to make a
http://nwalsh.com/            | decision, it is necessary not to make a
                              | decision.--Lord Falkland

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

Re: split-fancy and gnus-registry confusion

[Ted Zlatanov]

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

On Thu, 21 Feb 2008 12:09:24 -0500 Norman Walsh <ndw@nwalsh.com> wrote: 

NW> I'm completely confused by something.
NW> I'm using nnmail-split-fancy and gnus-registry-split-fancy-with-parent:
...

On Tue, 19 Feb 2008 18:41:19 -0500 Jake Colman <colman@ppllc.com> wrote: 

Jake> I just started seeing this come up when getting messages from my IMAP
Jake> server:

Jake> "gnus-registry-split-fancy-with-parent: too many extra matches for "

Jake> This just started today and I'm seeing several messages like this.

Jake> What's going on?!

The attached patch against today's CVS will give you proper logging,
plus I reworked the function gnus-registry-split-fancy-with-parent to be
much nicer.  Make sure you have gnus-verbose turned up to 9, then try
this out and let me know if the logging helped, and if things generally
worked OK.

I am reworking both logging and splitting, so comment on both please.
Anyone else interested in testing, please give it a shot.

Ted


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: registry.logging.patch --]
[-- Type: text/x-diff, Size: 9919 bytes --]

Index: gnus-registry.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/gnus-registry.el,v
retrieving revision 7.47
diff -a -u -r7.47 gnus-registry.el
--- gnus-registry.el	26 Feb 2008 18:16:38 -0000	7.47
+++ gnus-registry.el	27 Feb 2008 22:34:59 -0000
@@ -425,119 +425,150 @@
 For a message to be split, it looks for the parent message in the
 References or In-Reply-To header and then looks in the registry
 to see which group that message was put in.  This group is
-returned, unless it matches one of the entries in
-gnus-registry-unfollowed-groups or
-nnmail-split-fancy-with-parent-ignore-groups.
+returned, unless `gnus-registry-follow-group-p' return nil for
+that group.
 
 See the Info node `(gnus)Fancy Mail Splitting' for more details."
-  (let* ((refstr (or (message-fetch-field "references") "")) ; guarantee string
-	 (reply-to (message-fetch-field "in-reply-to"))	     ; grab reply-to
+  (let* ((refstr (or (message-fetch-field "references") "")) ; guaranteed
+	 (reply-to (message-fetch-field "in-reply-to"))	     ; may be nil
 	 ;; now, if reply-to is valid, append it to the References
 	 (refstr (if reply-to 
 		     (concat refstr " " reply-to)
 		   refstr))
-	(nnmail-split-fancy-with-parent-ignore-groups
-	 (if (listp nnmail-split-fancy-with-parent-ignore-groups)
-	     nnmail-split-fancy-with-parent-ignore-groups
-	   (list nnmail-split-fancy-with-parent-ignore-groups)))
-	res)
-    ;; the references string must be valid and parse to valid references
-    (if (and refstr (gnus-extract-references refstr))
-	(dolist (reference (nreverse (gnus-extract-references refstr)))
-	  (setq res (or (gnus-registry-fetch-group reference) res))
-	  (when (or (gnus-registry-grep-in-list
-		     res
-		     gnus-registry-unfollowed-groups)
-		    (gnus-registry-grep-in-list
-		     res
-		     nnmail-split-fancy-with-parent-ignore-groups))
-	    (setq res nil)))
-
-      ;; else: there were no references, now try the extra tracking
-      (let ((sender (gnus-string-remove-all-properties(message-fetch-field "from")))
-	    (subject (gnus-string-remove-all-properties
-		      (gnus-registry-simplify-subject
-		       (message-fetch-field "subject"))))
-	    (single-match t))
-	(when (and single-match
-		   (gnus-registry-track-sender-p)
-		   sender)
-	  (maphash
-	   (lambda (key value)
-	     (let ((this-sender (cdr
-				 (gnus-registry-fetch-extra key 'sender))))
-	       (when (and single-match
-			  this-sender
-			  (equal sender this-sender))
-		 ;; too many matches, bail
-		 (unless (equal res (gnus-registry-fetch-group key))
-		   (setq single-match nil))
-		 (setq res (gnus-registry-fetch-group key))
-		 (when (and sender res)
-		   (gnus-message
-		    ;; raise level of messaging if gnus-registry-track-extra
-		    (if gnus-registry-track-extra 7 9)
-		    "%s (extra tracking) traced sender %s to group %s"
-		    "gnus-registry-split-fancy-with-parent"
-		    sender
-		    res)))))
-	   gnus-registry-hashtb))
-	(when (and single-match
-		   (gnus-registry-track-subject-p)
-		   subject
-		   (< gnus-registry-minimum-subject-length (length subject)))
-	  (maphash
-	   (lambda (key value)
-	     (let ((this-subject (cdr
-				  (gnus-registry-fetch-extra key 'subject))))
-	       (when (and single-match
-			  this-subject
-			  (equal subject this-subject))
-		 ;; too many matches, bail
-		 (unless (equal res (gnus-registry-fetch-group key))
-		   (setq single-match nil))
-		 (setq res (gnus-registry-fetch-group key))
-		 (when (and subject res)
-		   (gnus-message
-		    ;; raise level of messaging if gnus-registry-track-extra
-		    (if gnus-registry-track-extra 7 9)
-		    "%s (extra tracking) traced subject %s to group %s"
-		    "gnus-registry-split-fancy-with-parent"
-		    subject
-		    res)))))
-	   gnus-registry-hashtb))
-	(unless single-match
-	  (gnus-message
-	   3
-	   "gnus-registry-split-fancy-with-parent: too many extra matches for %s"
-	   refstr)
-	  (setq res nil))))
-    (when (and refstr res)
-      (gnus-message
-       5
-       "gnus-registry-split-fancy-with-parent traced %s to group %s"
-       refstr res))
-
-    (when (and res gnus-registry-use-long-group-names)
-      (let ((m1 (gnus-find-method-for-group res))
-	    (m2 (or gnus-command-method
-		    (gnus-find-method-for-group gnus-newsgroup-name)))
-	    (short-res (gnus-group-short-name res)))
-      (if (gnus-methods-equal-p m1 m2)
-	  (progn
+	 ;; these may not be used, but the code is cleaner having them up here
+	 (sender (gnus-string-remove-all-properties
+		  (message-fetch-field "from")))
+	 (subject (gnus-string-remove-all-properties
+		   (gnus-registry-simplify-subject
+		    (message-fetch-field "subject"))))
+
+	 (nnmail-split-fancy-with-parent-ignore-groups
+	  (if (listp nnmail-split-fancy-with-parent-ignore-groups)
+	      nnmail-split-fancy-with-parent-ignore-groups
+	    (list nnmail-split-fancy-with-parent-ignore-groups)))
+	 (log-agent "gnus-registry-split-fancy-with-parent")
+	 found)
+
+    ;; this is a big if-else statement.  it uses
+    ;; gnus-registry-post-process-groups to filter the results after
+    ;; every step.
+    (cond
+     ;; the references string must be valid and parse to valid references
+     ((and refstr (gnus-extract-references refstr))
+      (dolist (reference (nreverse (gnus-extract-references refstr)))
+	(gnus-message
+	 9
+	 "%s is looking for matches for reference %s from [%s]"
+	 log-agent reference refstr)
+	(dolist (group (gnus-registry-fetch-groups reference))
+	  (when (and group (gnus-registry-follow-group-p group))
 	    (gnus-message
-	     9
-	     "gnus-registry-split-fancy-with-parent stripped group %s to %s"
-	     res
-	     short-res)
-	    (setq res short-res))
-	;; else...
+	     7
+	     "%s traced the reference %s from [%s] to group %s"
+	     log-agent reference refstr group)
+	    (push group found))))
+      ;; filter the found groups and return them
+      (setq found (gnus-registry-post-process-groups "references" refstr found)))
+
+     ;; else: there were no matches, now try the extra tracking by sender
+     ((and (gnus-registry-track-sender-p) 
+	   sender)
+      (maphash
+       (lambda (key value)
+	 (let ((this-sender (cdr
+			     (gnus-registry-fetch-extra key 'sender)))
+	       matches)
+	   (when (and this-sender
+		      (equal sender this-sender))
+	     (setq found (append (gnus-registry-fetch-groups key) found))
+	     (push key matches)
+	     (gnus-message
+	      ;; raise level of messaging if gnus-registry-track-extra
+	      (if gnus-registry-track-extra 7 9)
+	      "%s (extra tracking) traced sender %s to groups %s (keys %s)"
+	      log-agent sender found matches))))
+       gnus-registry-hashtb)
+      ;; filter the found groups and return them
+      (setq found (gnus-registry-post-process-groups "sender" sender found)))
+      
+     ;; else: there were no matches, now try the extra tracking by subject
+     ((and (gnus-registry-track-subject-p)
+	   subject
+	   (< gnus-registry-minimum-subject-length (length subject)))
+      (maphash
+       (lambda (key value)
+	 (let ((this-subject (cdr
+			      (gnus-registry-fetch-extra key 'subject)))
+	       matches)
+	   (when (and this-subject
+		      (equal subject this-subject))
+	     (setq found (append (gnus-registry-fetch-groups key) found))
+	     (push key matches)
+	     (gnus-message
+	      ;; raise level of messaging if gnus-registry-track-extra
+	      (if gnus-registry-track-extra 7 9)
+	      "%s (extra tracking) traced subject %s to groups %s (keys %s)"
+	      log-agent subject found matches))))
+       gnus-registry-hashtb)
+      ;; filter the found groups and return them
+      (setq found (gnus-registry-post-process-groups "subject" subject found))))))
+
+(defun gnus-registry-post-process-groups (mode key groups)
+  "Modifies GROUPS obtained by searching by MODE for KEY to determine which ones to follow.
+
+MODE can be 'subject' or 'sender' for example.  The KEY is the
+value by which MODE was searched.
+
+Transforms each group name to the equivalent short name.
+
+Checks if the current Gnus method (from `gnus-command-method' or
+from `gnus-newsgroup-name') is the same as the group's method.
+This is not possible if gnus-registry-use-long-group-names is
+false.  Foreign methods are not supported so they are rejected.
+
+Reduces the list to a single group, or complains if that's not
+possible."
+  (let ((log-agent "gnus-registry-post-process-group")
+	out)
+    (if gnus-registry-use-long-group-names
+	(dolist (group groups)
+	  (let ((m1 (gnus-find-method-for-group group))
+		(m2 (or gnus-command-method
+			(gnus-find-method-for-group gnus-newsgroup-name)))
+		(short-name (gnus-group-short-name group)))
+	    (if (gnus-methods-equal-p m1 m2)
+		(progn
+		  ;; this is REALLY just for debugging
+		  (gnus-message
+		   10
+		   "%s stripped group %s to %s"
+		   log-agent group short-name)
+		  (unless (member short-name out)
+		    (push short-name out)))
+	      ;; else...
+	      (gnus-message
+	       7
+	       "%s ignored foreign group %s"
+	       log-agent group))))
+      (setq out groups))
+    (when (cdr-safe out)
 	(gnus-message
-	 7
-	 "gnus-registry-split-fancy-with-parent ignored foreign group %s"
-	 res)
-	(setq res nil))))
-    res))
+	 5
+	 "%s: too many extra matches (%s) for %s %s.  Returning none."
+	 log-agent out mode key)
+	(setq out nil))
+    out))
+
+(defun gnus-registry-follow-group-p (group)
+  "Determines if a group name should be followed.
+Consults `gnus-registry-unfollowed-groups' and
+`nnmail-split-fancy-with-parent-ignore-groups'."
+  (not (or (gnus-registry-grep-in-list
+	    group
+	    gnus-registry-unfollowed-groups)
+	   (gnus-registry-grep-in-list
+	    group
+	    nnmail-split-fancy-with-parent-ignore-groups))))
 
 (defun gnus-registry-wash-for-keywords (&optional force)
   (interactive)

Re: split-fancy and gnus-registry confusion

[Jake Colman]

>>>>> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:

   TZ> The attached patch against today's CVS will give you proper
   TZ> logging, plus I reworked the function
   TZ> gnus-registry-split-fancy-with-parent to be much nicer.  Make
   TZ> sure you have gnus-verbose turned up to 9, then try this out and
   TZ> let me know if the logging helped, and if things generally worked
   TZ> OK.

   TZ> I am reworking both logging and splitting, so comment on both
   TZ> please.  Anyone else interested in testing, please give it a
   TZ> shot.

   TZ> Ted

I am up and running with gnus from 20080228 with your patch.  It must be
working because the registry has got a heck of alot more to say!

Below are two examples: one tha(I guess) did as it should and the other
complaining about extra matches.  What exactly is this telling me?  How
do I read this?

gnus-registry-split-fancy-with-parent (extra tracking) traced sender "Rafiq Ahmed" <rafiq.ahmed@Xoriant.Com> to groups (INBOX/Principia/StateControl INBOX/Principia/SFP INBOX/Principia/Management INBOX/Principia/SFP INBOX/Principia/SFP INBOX/Principia/StateControl INBOX/Principia/SFP INBOX/Principia/SFP INBOX/Principia/SFP INBOX/Principia/Management INBOX/Principia/SFP INBOX/Principia/StateControl INBOX/Principia/StateControl INBOX/Principia/StateControl INBOX/Principia/StateControl INBOX/Principia/SFP INBOX/Principia/StateControl INBOX/Principia/SFP INBOX/Principia/StateControl INBOX/Principia/StateControl) (keys (<FA3D7C54DA3A1540B2C92C93ACD2156002A32CFE@XOREXCH.India.XoriantCorp.com>))

gnus-registry-post-process-group: too many extra matches ((INBOX/Principia/StateControl INBOX/Principia/SFP INBOX/Principia/Management INBOX/Principia/SFP INBOX/Principia/SFP INBOX/Principia/StateControl INBOX/Principia/SFP INBOX/Principia/SFP INBOX/Principia/SFP INBOX/Principia/Management INBOX/Principia/SFP INBOX/Principia/StateControl INBOX/Principia/StateControl INBOX/Principia/StateControl INBOX/Principia/StateControl INBOX/Principia/SFP INBOX/Principia/StateControl INBOX/Principia/SFP INBOX/Principia/StateControl INBOX/Principia/StateControl)) for sender "Rafiq Ahmed" <rafiq.ahmed@Xoriant.Com>.  Returning none.

Thanks.

...Jake

-- 
Jake Colman
Director of Software Development
Principia Partners LLC
101 West Elm Street
Suite 620
Conshohocken, PA  19428
+1 (610) 755-9786
www.principiapartners.com

Re: split-fancy and gnus-registry confusion

[Ted Zlatanov]

On Thu, 28 Feb 2008 09:09:22 -0500 Jake Colman <colman@ppllc.com> wrote: 

>>>>>> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:
TZ> The attached patch against today's CVS will give you proper
TZ> logging, plus I reworked the function
TZ> gnus-registry-split-fancy-with-parent to be much nicer.  Make
TZ> sure you have gnus-verbose turned up to 9, then try this out and
TZ> let me know if the logging helped, and if things generally worked
TZ> OK.

TZ> I am reworking both logging and splitting, so comment on both
TZ> please.  Anyone else interested in testing, please give it a
TZ> shot.

TZ> Ted

JC> I am up and running with gnus from 20080228 with your patch.  It must be
JC> working because the registry has got a heck of alot more to say!

JC> Below are two examples: one tha(I guess) did as it should and the other
JC> complaining about extra matches.  What exactly is this telling me?  How
JC> do I read this?

JC> gnus-registry-split-fancy-with-parent (extra tracking) traced sender "Rafiq Ahmed" <rafiq.ahmed@Xoriant.Com> to groups (INBOX/Principia/StateControl INBOX/Principia/SFP INBOX/Principia/Management INBOX/Principia/SFP INBOX/Principia/SFP INBOX/Principia/StateControl INBOX/Principia/SFP INBOX/Principia/SFP INBOX/Principia/SFP INBOX/Principia/Management INBOX/Principia/SFP INBOX/Principia/StateControl INBOX/Principia/StateControl INBOX/Principia/StateControl INBOX/Principia/StateControl INBOX/Principia/SFP INBOX/Principia/StateControl INBOX/Principia/SFP INBOX/Principia/StateControl INBOX/Principia/StateControl) (keys (<FA3D7C54DA3A1540B2C92C93ACD2156002A32CFE@XOREXCH.India.XoriantCorp.com>))

JC> gnus-registry-post-process-group: too many extra matches ((INBOX/Principia/StateControl INBOX/Principia/SFP INBOX/Principia/Management INBOX/Principia/SFP INBOX/Principia/SFP INBOX/Principia/StateControl INBOX/Principia/SFP INBOX/Principia/SFP INBOX/Principia/SFP INBOX/Principia/Management INBOX/Principia/SFP INBOX/Principia/StateControl INBOX/Principia/StateControl INBOX/Principia/StateControl INBOX/Principia/StateControl INBOX/Principia/SFP INBOX/Principia/StateControl INBOX/Principia/SFP INBOX/Principia/StateControl INBOX/Principia/StateControl)) for sender "Rafiq Ahmed" <rafiq.ahmed@Xoriant.Com>.  Returning none.

I think this is one splitting example with two output lines.  The
registry found matches by sender, then in
gnus-registry-post-process-group the matches were filtered.

The post-processing says that the sender has multiple messages, whose
registry entries point to several different groups.  Currently the
registry post-processing just gives up if that happens, so you don't end
up with inconsistent splitting.  I could change that logic, since I've
reworked the splitting code anyhow.  Maybe the user could set a
strategy:

- give up on multiples (current)

- select first group alphabetically or some other stable sort method
  (predictable, easy to understand, easy to implement, not necessarily
  accurate)

- select a group if it's "preferred" (configuration burden is on the
  user)

- ask user (annoying if it happens a lot, but the "preferred" list of
  groups could be learned dynamically this way)

- some mix of the above

- other ideas?

Ted

gnus-registry logging and splitting improvements (was: split-fancy and gnus-registry confusion)

[Ted Zlatanov]

On Wed, 27 Feb 2008 16:40:29 -0600 Ted Zlatanov <tzz@lifelogs.com> wrote: 

TZ> The attached patch against today's CVS will give you proper logging,
TZ> plus I reworked the function gnus-registry-split-fancy-with-parent to be
TZ> much nicer.  Make sure you have gnus-verbose turned up to 9, then try
TZ> this out and let me know if the logging helped, and if things generally
TZ> worked OK.

I comitted this patch after running with it for a bit, and Jake Colman
reported it worked for him as well.  Please note that I rewrote much of
the splitting code, so it's possible some bugs have crept in.

Ted

Re: split-fancy and gnus-registry confusion

[Ted Zlatanov]

On Thu, 21 Feb 2008 12:09:24 -0500 Norman Walsh <ndw@nwalsh.com> wrote: 

NW> If I put the cursor in that message and run 
NW> (gnus-registry-split-fancy-with-parent), it returns "nil", as I'd expect.

NW> But if I do B t, I get:

NW> (: gnus-registry-split-fancy-with-parent)
NW> "misc"
NW> (: nwalsh-incoming-group)
NW> "archive.2008-02"

NW> which I find totally baffling. Where is that 'misc' coming from?

NW> Note that gnus-registry-track-extra is nil.

NW> Any clues you can provide would be most helpful.

Just from what you've described, I have no idea, sorry.  If you can
re-run your example with the new registry changes, I could try to
understand what happened.

Ted

Re: split-fancy and gnus-registry confusion

[Norman Walsh]

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

/ Ted Zlatanov <tzz@lifelogs.com> was heard to say:
| On Thu, 21 Feb 2008 12:09:24 -0500 Norman Walsh <ndw@nwalsh.com> wrote: 
|
| NW> If I put the cursor in that message and run 
| NW> (gnus-registry-split-fancy-with-parent), it returns "nil", as I'd expect.
|
| NW> But if I do B t, I get:
|
| NW> (: gnus-registry-split-fancy-with-parent)
| NW> "misc"
| NW> (: nwalsh-incoming-group)
| NW> "archive.2008-02"
|
| NW> which I find totally baffling. Where is that 'misc' coming from?
|
| NW> Note that gnus-registry-track-extra is nil.
|
| NW> Any clues you can provide would be most helpful.
|
| Just from what you've described, I have no idea, sorry.  If you can
| re-run your example with the new registry changes, I could try to
| understand what happened.

I have the new code, I think. I updated from CVS and the patch seemed
to have already been applied.

I set gnus-verbosity to 9 and tried "B" "t" on the offending message,
but didn't get any useful feedback. Is there something else I should
have done?

                                        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 --]

Re: split-fancy and gnus-registry confusion

[Ted Zlatanov]

On Mon, 03 Mar 2008 11:07:11 -0500 Norman Walsh <ndw@nwalsh.com> wrote: 

NW> I have the new code, I think. I updated from CVS and the patch seemed
NW> to have already been applied.

Yes, I did it last week after running for a bit without problems and
without bug reports.

NW> I set gnus-verbosity to 9 and tried "B" "t" on the offending message,
NW> but didn't get any useful feedback. Is there something else I should
NW> have done?

Are you sure you got nothing?  If so, then `B t' may not have called
gnus-registry-split-fancy-with-parent.  Try running it manually:

M-: (gnus-registry-split-fancy-with-parent)

in the article buffer with the headers visible (hit `t').

Ted

Re: split-fancy and gnus-registry confusion

[Norman Walsh]

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

/ Ted Zlatanov <tzz@lifelogs.com> was heard to say:
| Are you sure you got nothing?  If so, then `B t' may not have called
| gnus-registry-split-fancy-with-parent.  Try running it manually:
|
| M-: (gnus-registry-split-fancy-with-parent)
|
| in the article buffer with the headers visible (hit `t').

It reports "nil" but gives no other debugging messages. 'B t' still
reports "misc" which is (still) wrong.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | We dance around in a ring and suppose,
http://nwalsh.com/            | but the Secret sits in the middle and
                              | knows.--Robert Frost

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

Re: split-fancy and gnus-registry confusion

[Ted Zlatanov]

On Tue, 04 Mar 2008 12:14:35 -0500 Norman Walsh <ndw@nwalsh.com> wrote: 

NW> / Ted Zlatanov <tzz@lifelogs.com> was heard to say:
NW> | Are you sure you got nothing?  If so, then `B t' may not have called
NW> | gnus-registry-split-fancy-with-parent.  Try running it manually:
NW> |
NW> | M-: (gnus-registry-split-fancy-with-parent)
NW> |
NW> | in the article buffer with the headers visible (hit `t').

NW> It reports "nil" but gives no other debugging messages. 'B t' still
NW> reports "misc" which is (still) wrong.

Set gnus-verbose to 9.

Run both commands.

Look in the *Messages* buffer for the debug output.

Thanks
Ted

Re: split-fancy and gnus-registry confusion

[Norman Walsh]

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

/ Ted Zlatanov <tzz@lifelogs.com> was heard to say:
| On Tue, 04 Mar 2008 12:14:35 -0500 Norman Walsh <ndw@nwalsh.com> wrote: 
|
| NW> / Ted Zlatanov <tzz@lifelogs.com> was heard to say:
| NW> | Are you sure you got nothing?  If so, then `B t' may not have called
| NW> | gnus-registry-split-fancy-with-parent.  Try running it manually:
| NW> |
| NW> | M-: (gnus-registry-split-fancy-with-parent)
| NW> |
| NW> | in the article buffer with the headers visible (hit `t').
|
| NW> It reports "nil" but gives no other debugging messages. 'B t' still
| NW> reports "misc" which is (still) wrong.
|
| Set gnus-verbose to 9.
|
| Run both commands.
|
| Look in the *Messages* buffer for the debug output.

That's exactly what I did.

I'm running No Gnus v0.7 from CVS of a few days ago, after you checked in
your changes. I've set gnus-verbose to 9.

When *new* mail comes in, I do get some more verbose messages:

gnus-registry-split-fancy-with-parent traced the reference
<47CD9E45.8080607@sun.com> from [<4787B193.4030800@sun.com>
<4790EC1F.3080009@sun.com> <47A11939.1050101@sun.com>
<47A89F04.9030306@sun.com> <47B1E6F8.4050101@sun.com>
<47BB12F1.4030906@sun.com> <47C46361.4050001@sun.com>
<47CD9E45.8080607@sun.com> <47CD9E45.8080607@sun.com>] to group
sun.jaxp-tech-internal

But when I go to an essay in a *Summary* buffer that I know was misplaced,
expand the headers, switch to that buffer, and M-: 
 (gnus-registry-split-fancy-with-parent), I get "nil" in the minibuffer
and "nil" in the *Messages* buffer.

When I run "B t", I get 

(: gnus-registry-split-fancy-with-parent)
"misc"
(: nwalsh-incoming-group)
"archive.2008-03"

and "This message would go to archive.2008-03, misc" in *Messages*

I'm very confused. This looks and feels like user error, but I don't
see where I've erred.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | What is familiar is what we are used
http://nwalsh.com/            | to; and what we are used to is most
                              | difficult to 'Know'--that is, to see as
                              | a problem; that is, to see as strange,
                              | as distant, as 'outside us'.-- Nietzsche

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

Re: split-fancy and gnus-registry confusion

[Ted Zlatanov]

On Tue, 04 Mar 2008 16:14:18 -0500 Norman Walsh <ndw@nwalsh.com> wrote: 

NW> / Ted Zlatanov <tzz@lifelogs.com> was heard to say:
NW> | On Tue, 04 Mar 2008 12:14:35 -0500 Norman Walsh <ndw@nwalsh.com> wrote: 
NW> |
NW> | NW> / Ted Zlatanov <tzz@lifelogs.com> was heard to say:
NW> | NW> | Are you sure you got nothing?  If so, then `B t' may not have called
NW> | NW> | gnus-registry-split-fancy-with-parent.  Try running it manually:
NW> | NW> |
NW> | NW> | M-: (gnus-registry-split-fancy-with-parent)
NW> | NW> |
NW> | NW> | in the article buffer with the headers visible (hit `t').
NW> |
NW> | NW> It reports "nil" but gives no other debugging messages. 'B t' still
NW> | NW> reports "misc" which is (still) wrong.
NW> |
NW> | Set gnus-verbose to 9.
NW> |
NW> | Run both commands.
NW> |
NW> | Look in the *Messages* buffer for the debug output.

NW> That's exactly what I did.

NW> I'm running No Gnus v0.7 from CVS of a few days ago, after you checked in
NW> your changes. I've set gnus-verbose to 9.

NW> When *new* mail comes in, I do get some more verbose messages:

NW> gnus-registry-split-fancy-with-parent traced the reference
NW> <47CD9E45.8080607@sun.com> from [<4787B193.4030800@sun.com>
NW> <4790EC1F.3080009@sun.com> <47A11939.1050101@sun.com>
NW> <47A89F04.9030306@sun.com> <47B1E6F8.4050101@sun.com>
NW> <47BB12F1.4030906@sun.com> <47C46361.4050001@sun.com>
NW> <47CD9E45.8080607@sun.com> <47CD9E45.8080607@sun.com>] to group
NW> sun.jaxp-tech-internal

NW> But when I go to an essay in a *Summary* buffer that I know was misplaced,
NW> expand the headers, switch to that buffer, and M-: 
NW>  (gnus-registry-split-fancy-with-parent), I get "nil" in the minibuffer
NW> and "nil" in the *Messages* buffer.

NW> When I run "B t", I get 

NW> (: gnus-registry-split-fancy-with-parent)
NW> "misc"
NW> (: nwalsh-incoming-group)
NW> "archive.2008-03"

NW> and "This message would go to archive.2008-03, misc" in *Messages*

NW> I'm very confused. This looks and feels like user error, but I don't
NW> see where I've erred.

`B t' and gnus-registry-split-fancy-with-parent must not be working
right, or your gnus-verbose value is set to a lower value somewhere
else.  Would it be possible to see the message you are using for
testing, in case something about it is the problem?  Send it to me
privately if necessary.  You can also try

M-: (let ((gnus-verbose 9)) (gnus-registry-split-fancy-with-parent))

which is guaranteed to work because it will override gnus-verbose.  If
it doesn't produce anything in *Messages*, something is wrong on your
side.

Ted

Re: split-fancy and gnus-registry confusion

[Norman Walsh]

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

/ Ted Zlatanov <tzz@lifelogs.com> was heard to say:
[...]
| `B t' and gnus-registry-split-fancy-with-parent must not be working
| right, or your gnus-verbose value is set to a lower value somewhere
| else.  Would it be possible to see the message you are using for
| testing, in case something about it is the problem?  Send it to me
| privately if necessary.  You can also try
|
| M-: (let ((gnus-verbose 9)) (gnus-registry-split-fancy-with-parent))
|
| which is guaranteed to work because it will override gnus-verbose.  If
| it doesn't produce anything in *Messages*, something is wrong on your
| side.

That did it. I wonder where gnus-verbose is getting reset? I set it in
*scratch* and it *seemed* persistent. Anyway...

Here's what I get for one of the misfiled messages:

gnus-registry-split-fancy-with-parent is looking for matches for reference <m23ar738ty.fsf@nwalsh.com> from [ <m23ar738ty.fsf@nwalsh.com>]
gnus-registry-split-fancy-with-parent traced the reference <m23ar738ty.fsf@nwalsh.com> from [ <m23ar738ty.fsf@nwalsh.com>] to group nnml:misc
gnus-registry-split-fancy-with-parent traced the reference <m23ar738ty.fsf@nwalsh.com> from [ <m23ar738ty.fsf@nwalsh.com>] to group w3c.member.tag
gnus-registry-post-process-group: too many extra matches ((misc w3c.member.tag)) for references  <m23ar738ty.fsf@nwalsh.com>.  Returning none.
nil

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:

X-From-Line: ndw  Mon Mar  3 14:34:19 2008
Return-path: <tag-request@frink.w3.org>
Received: from mail-amer.sun.com [192.18.109.69]
	by traytable.local with IMAP (fetchmail-6.3.8)
	for <ndw@localhost> (single-drop); Mon, 03 Mar 2008 14:34:19 -0500 (EST)
Received: from fe-amer-09.sun.com ([192.18.109.79])
 by amer4-mail1.central.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTP id <0JX600ILX66EWX80@amer4-mail1.central.sun.com> for
 ndw@amer4-mail1.Central.Sun.COM; Mon, 03 Mar 2008 12:30:14 -0700 (MST)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JX600L014G92000@mail-amer.sun.com> for ndw@amer4-mail1.Central.Sun.COM
 (ORCPT Norman.Walsh@Sun.COM); Mon, 03 Mar 2008 12:30:14 -0700 (MST)
Received: from phys-amer4-1.central.sun.com ([129.147.157.48])
 by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTP id <0JX60075565E3UH0@mail-amer.sun.com> for
 ndw@amer4-mail1.Central.Sun.COM (ORCPT Norman.Walsh@Sun.COM); Mon,
 03 Mar 2008 12:29:38 -0700 (MST)
Received: from dm-east-01.east.sun.com ([129.148.9.192])
 by amer4-mail1.central.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTP id <0JX600IBH65EWX80@amer4-mail1.central.sun.com> for
 ndw@amer4-mail1.Central.Sun.COM (ORCPT Norman.Walsh@Sun.COM); Mon,
 03 Mar 2008 12:29:38 -0700 (MST)
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by dm-east-01.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2)
 with ESMTP id m23JTbga016150	for <norman.walsh@east.sun.com>; Mon,
 03 Mar 2008 14:29:38 -0500 (EST)
Received: from brm-avmta-1.central.sun.com
 (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2)
 with ESMTP id m23JTaaR014042	for
 <@sunmail2sca.sfbay.sun.com:Norman.Walsh@sun.com>; Mon,
 03 Mar 2008 19:29:37 +0000 (GMT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JX600A0165DRB00@brm-avmta-1.central.sun.com> for Norman.Walsh@sun.com
 (ORCPT Norman.Walsh@Sun.COM); Mon, 03 Mar 2008 12:29:37 -0700 (MST)
Received: from sca-ea-mail-2.sun.com ([192.18.43.25])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JX6005JY658OV70@brm-avmta-1.central.sun.com> for
 Norman.Walsh@sun.com (ORCPT Norman.Walsh@Sun.COM); Mon,
 03 Mar 2008 12:29:36 -0700 (MST)
Received: from relay22.sun.com
 (relay22.sun.com [192.12.251.34] (may be forged))	by sca-ea-mail-2.sun.com
 (8.13.7+Sun/8.12.9) with ESMTP id m23JHlv2004571	for <Norman.Walsh@Sun.COM>;
 Mon, 03 Mar 2008 19:29:31 +0000 (GMT)
Received: from mms24es.sun.com ([150.143.232.74] [150.143.232.74])
 by relay22i.sun.com with ESMTP id BT-MMP-661917 for Norman.Walsh@Sun.COM; Mon,
 03 Mar 2008 19:29:31 +0000 (Z)
Received: from relay22.sun.com (relay22.sun.com [192.12.251.34])
 by mms24es.sun.com with ESMTP id BT-MMP-2254236 for Norman.Walsh@Sun.COM; Mon,
 03 Mar 2008 19:29:29 +0000 (Z)
Received: from frink.w3.org ([128.30.52.56] [128.30.52.56])
 by relay22i.sun.com with ESMTP id BT-MMP-14977927 for Norman.Walsh@Sun.COM;
 Mon, 03 Mar 2008 19:29:29 +0000 (Z)
Received: from lists by frink.w3.org with local (Exim 4.63)
	(envelope-from <tag-request@listhub.w3.org>)
	id 1JWGLp-0003wi-0i	for tag-dist@listhub.w3.org; Mon,
 03 Mar 2008 19:29:29 +0000
Received: from aji.w3.org ([133.27.228.225])	by frink.w3.org with esmtp
 (Exim 4.63)	(envelope-from <ndw@nwalsh.com>)
	id 1JWGLn-0003vw-VJ	for tag@listhub.w3.org; Mon, 03 Mar 2008 19:29:28 +0000
Received: from mho-01-bos.mailhop.org ([63.208.196.178])
	by aji.w3.org with esmtp (Exim 4.63)	(envelope-from <ndw@nwalsh.com>)
	id 1JWGLh-00009g-9h	for tag@w3.org; Mon, 03 Mar 2008 19:29:27 +0000
Received: from 66-189-4-239.dhcp.oxfr.ma.charter.com
 ([66.189.4.239] helo=localhost)	by mho-01-bos.mailhop.org with esmtpsa
 (TLSv1:AES128-SHA:128)	(Exim 4.68)	(envelope-from <ndw@nwalsh.com>)
	id 1JWGLc-000DG8-IG; Mon, 03 Mar 2008 19:29:16 +0000
X-URL: http://nwalsh.com/
Resent-date: Mon, 03 Mar 2008 19:29:29 +0000
Date: Mon, 03 Mar 2008 14:29:13 -0500
Resent-from: tag@w3.org
From: Norman Walsh <ndw@nwalsh.com>
Subject: @profile in RDFa
X-Originating-IP: 66.189.4.239
Resent-sender: tag-request@w3.org
Sender: tag-request@w3.org
To: tag@w3.org
Resent-message-id: <E1JWGLp-0003wi-0i@frink.w3.org>
X-Gnus-Mail-Source: file:/var/mail/ndw
Message-id: <m23ar738ty.fsf@nwalsh.com>
MIME-version: 1.0
Content-type: multipart/signed; boundary="=-=-=";
 protocol="application/pgp-signature"; micalg=pgp-sha1
Precedence: list
X-Loop: tag@w3.org
Received-SPF: none
Archived-At: <http://www.w3.org/mid/m23ar738ty.fsf@nwalsh.com>
X-PMX-Version: 5.2.0.264296
X-Brightmail-Tracker: AAAAAA==
X-Mail-Handler: MailHop Outbound by DynDNS
X-Report-Abuse-To: abuse@dyndns.com (see
 http://www.mailhop.org/outbound/abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1+3Y0hgP5VlFF/6Z1N4TJ9r
X-Countdown: T-minus 46 weeks, 16 hours, 31 minutes, 25 seconds
X-SPF-Guess: neutral
X-W3C-Hub-Spam-Report: BAYES_00=-2.599
X-W3C-Hub-Spam-Status: No, score=-2.6
X-W3C-Scan-Sig: aji.w3.org 1JWGLh-00009g-9h 66007be6669514f6c14dc02bfcb07f37
X-Original-To: tag@w3.org
X-Antispam: No, score=-2.6/5.0, scanned in 2.036sec at (localhost [127.0.0.1])
	by smf-spamd v1.3.1 - http://smfs.sf.net/
X-Mailing-List: <tag@w3.org> archive/latest/5660
List-Unsubscribe: <mailto:tag-request@w3.org?subject=unsubscribe>
List-Help: <http://www.w3.org/Mail/>
List-Id: <tag.w3.org>
User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1.50 (darwin)
Original-recipient: rfc822;Norman.Walsh@Sun.COM
Xref: nwalsh.com w3c.member.tag:6123
Lines: 30

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?

Here are the headers for the message that got misfiled, in case they help:

X-From-Line: ndw  Wed Mar  5 07:36:13 2008
Return-path: <tag-request@frink.w3.org>
Received: from mail-amer.sun.com [192.18.109.69]
	by traytable.local with IMAP (fetchmail-6.3.8)
	for <ndw@localhost> (single-drop); Wed, 05 Mar 2008 07:36:13 -0500 (EST)
Received: from fe-amer-09.sun.com ([192.18.109.79])
 by amer4-mail1.central.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTP id <0JX80019WV0UOY30@amer4-mail1.central.sun.com> for
 ndw@amer4-mail1.Central.Sun.COM; Tue, 04 Mar 2008 23:22:06 -0700 (MST)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JX800601UU36J00@mail-amer.sun.com> for ndw@amer4-mail1.Central.Sun.COM
 (ORCPT Norman.Walsh@Sun.COM); Tue, 04 Mar 2008 23:22:06 -0700 (MST)
Received: from phys-amer4-1.central.sun.com ([129.147.157.48])
 by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTP id <0JX800GRIV0UR260@mail-amer.sun.com> for
 ndw@amer4-mail1.Central.Sun.COM (ORCPT Norman.Walsh@Sun.COM); Tue,
 04 Mar 2008 23:22:06 -0700 (MST)
Received: from dm-east-02.east.sun.com ([129.148.13.5])
 by amer4-mail1.central.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTP id <0JX80019SV0TOY30@amer4-mail1.central.sun.com> for
 ndw@amer4-mail1.Central.Sun.COM (ORCPT Norman.Walsh@Sun.COM); Tue,
 04 Mar 2008 23:22:06 -0700 (MST)
Received: from sunmail4.singapore.sun.com
 (sunmail4.Singapore.Sun.COM [129.158.71.19])	by dm-east-02.east.sun.com
 (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m256M4WG019048	for
 <norman.walsh@east.sun.com>; Wed, 05 Mar 2008 01:22:05 -0500 (EST)
Received: from nwk-avmta-1.SFBay.Sun.COM
 (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])	by sunmail4.singapore.sun.com
 (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m256LtwG013095	for
 <@sunmail2sca.sfbay.sun.com:Norman.Walsh@sun.com>; Wed,
 05 Mar 2008 14:22:03 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JX800D0JV0P5Z00@nwk-avmta-1.sfbay.Sun.COM> for Norman.Walsh@sun.com
 (ORCPT Norman.Walsh@Sun.COM); Tue, 04 Mar 2008 22:22:01 -0800 (PST)
Received: from brmea-mail-1.sun.com ([192.18.98.31])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JX8003PCV0PJO60@nwk-avmta-1.sfbay.Sun.COM> for
 Norman.Walsh@sun.com (ORCPT Norman.Walsh@Sun.COM); Tue,
 04 Mar 2008 22:22:01 -0800 (PST)
Received: from relay16i.sun.com
 (ip126.net129179-4.block1.us.syntegra.com [129.179.4.126])
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m256M0lC013104	for
 <Norman.Walsh@Sun.COM>; Wed, 05 Mar 2008 06:22:01 +0000 (GMT)
Received: from mmp14es.sun.com ([160.41.209.24] [160.41.209.24])
 by relay16i.sun.com with ESMTP id BT-MMP-893582 for Norman.Walsh@Sun.COM; Wed,
 05 Mar 2008 06:22:00 +0000 (Z)
Received: from relay11i.sun.com (relay11i.sun.com [129.179.4.121])
 by mmp14es.sun.com with ESMTP id BT-MMP-92295 for Norman.Walsh@Sun.COM; Wed,
 05 Mar 2008 06:22:00 +0000 (Z)
Received: from frink.w3.org ([128.30.52.56] [128.30.52.56])
 by relay1i.sun.com with ESMTP id BT-MMP-248604 for Norman.Walsh@Sun.COM; Wed,
 05 Mar 2008 06:22:00 +0000 (Z)
Received: from lists by frink.w3.org with local (Exim 4.63)
	(envelope-from <tag-request@listhub.w3.org>)
	id 1JWn0n-0004SH-Q5	for tag-dist@listhub.w3.org; Wed,
 05 Mar 2008 06:21:57 +0000
Received: from lisa.w3.org ([128.30.52.41])	by frink.w3.org with esmtp
 (Exim 4.63)	(envelope-from <noah_mendelsohn@us.ibm.com>)
	id 1JWn0m-0004RU-Eb	for tag@listhub.w3.org; Wed, 05 Mar 2008 06:21:56 +0000
Received: from e31.co.us.ibm.com ([32.97.110.149])	by lisa.w3.org with esmtp
 (Exim 4.63)	(envelope-from <noah_mendelsohn@us.ibm.com>)
	id 1JWn0f-0001cn-Kt	for tag@w3.org; Wed, 05 Mar 2008 06:21:55 +0000
Received: from d03relay04.boulder.ibm.com
 (d03relay04.boulder.ibm.com [9.17.195.106])
	by e31.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id m256LgmK007832	for
 <tag@w3.org>; Wed, 05 Mar 2008 01:21:42 -0500
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170])
	by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v8.7)
 with ESMTP id m256Lfcp187240	for <tag@w3.org>; Tue, 04 Mar 2008 23:21:41 -0700
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1])
	by d03av04.boulder.ibm.com (8.12.11.20060308/8.13.3)
 with ESMTP id m256LfQ0024459	for <tag@w3.org>; Tue, 04 Mar 2008 23:21:41 -0700
Received: from internet1.lotus.com (internet1.lotus.com [9.33.9.11])
	by d03av04.boulder.ibm.com (8.12.11.20060308/8.12.11)
 with ESMTP id m256Lelh024403
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue,
 04 Mar 2008 23:21:41 -0700
Received: from wtfmail05a.lotus.com (wtfmail05a.lotus.com [9.33.9.125])
	by internet1.lotus.com (8.14.1/8.14.1) with ESMTP id m256LV1M010496; Wed,
 05 Mar 2008 01:21:32 -0500 (EST)
Resent-date: Wed, 05 Mar 2008 06:21:57 +0000
Date: Wed, 05 Mar 2008 01:22:30 -0500
Resent-from: tag@w3.org
From: noah_mendelsohn@us.ibm.com
Subject: Re: @profile in RDFa
In-reply-to: <m23ar738ty.fsf@nwalsh.com>
Resent-sender: tag-request@w3.org
Sender: tag-request@w3.org
To: Norman Walsh <ndw@nwalsh.com>
Cc: tag@w3.org
Resent-message-id: <E1JWn0n-0004SH-Q5@frink.w3.org>
X-Gnus-Mail-Source: file:/var/mail/ndw
Message-id: <OF08B19F66.319141D1-ON85257402.00686E68-85257403.0022EF8B@lotus.com>
MIME-version: 1.0
X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006
Content-type: multipart/mixed; boundary="Boundary_(ID_/tL5g0sbn+ndzxlRwo48Ew)"
X-MIMETrack: Serialize by Router on WTFMAIL05a/WTF/M/Lotus(Release 8.0|August
 02, 2007) at 03/05/2008 01:22:36 AM
Precedence: list
X-Loop: tag@w3.org
Received-SPF: pass
Archived-At:
 <http://www.w3.org/mid/OF08B19F66.319141D1-ON85257402.00686E68-85257403.0022EF8B@lotus.com>
X-PMX-Version: 5.2.0.264296
X-Brightmail-Tracker: AAAAAA==
X-KeepSent: 08B19F66:319141D1-85257402:00686E68; type=4; name=$KeepSent
X-SPF-Guess: pass
X-W3C-Hub-Spam-Status: No, score=-6.6
X-W3C-Hub-Spam-Report: BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1JWn0f-0001cn-Kt a33277f66b6b9cc261689aaec9ecfb1d
X-Original-To: tag@w3.org
X-Antispam: No, score=-2.6/5.0, scanned in 0.269sec at (localhost [127.0.0.1])
	by smf-spamd v1.3.1 - http://smfs.sf.net/
X-Mailing-List: <tag@w3.org> archive/latest/5665
List-Unsubscribe: <mailto:tag-request@w3.org?subject=unsubscribe>
List-Help: <http://www.w3.org/Mail/>
List-Id: <tag.w3.org>
Original-recipient: rfc822;Norman.Walsh@Sun.COM
Lines: 68
Xref: nwalsh.com misc:135704 archive.2008-03:1380

                                        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 --]

Re: split-fancy and gnus-registry confusion

[Norman Walsh]

[-- 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 --]

Re: split-fancy and gnus-registry confusion

[Ted Zlatanov]

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

Re: split-fancy and gnus-registry confusion

[Ted Zlatanov]

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