Gnus development mailing list
 help / color / mirror / Atom feed
From: Norman Walsh <ndw@nwalsh.com>
To: ding@gnus.org
Subject: split-fancy and gnus-registry confusion
Date: Thu, 21 Feb 2008 12:09:24 -0500	[thread overview]
Message-ID: <m27igy9qyj.fsf@nwalsh.com> (raw)

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

             reply	other threads:[~2008-02-21 17:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21 17:09 Norman Walsh [this message]
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

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=m27igy9qyj.fsf@nwalsh.com \
    --to=ndw@nwalsh.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).