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 11:19:17 -0600	[thread overview]
Message-ID: <86r6eq9zl6.fsf@lifelogs.com> (raw)
In-Reply-To: <m2lk4ytnr8.fsf@nwalsh.com> (Norman Walsh's message of "Tue, 04 Mar 2008 12:14:35 -0500")

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



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