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: Tue, 04 Mar 2008 16:14:18 -0500 [thread overview]
Message-ID: <m2y78yqjit.fsf@nwalsh.com> (raw)
In-Reply-To: <86r6eq9zl6.fsf@lifelogs.com>
[-- 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 --]
next prev parent reply other threads:[~2008-03-04 21:14 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 [this message]
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=m2y78yqjit.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).