Gnus development mailing list
 help / color / mirror / Atom feed
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: Tue, 04 Mar 2008 15:24:44 -0600	[thread overview]
Message-ID: <86fxv69o83.fsf@lifelogs.com> (raw)
In-Reply-To: <m2y78yqjit.fsf@nwalsh.com> (Norman Walsh's message of "Tue, 04 Mar 2008 16:14:18 -0500")

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



  reply	other threads:[~2008-03-04 21:24 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 [this message]
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=86fxv69o83.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).