From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Totally incorrect splitting
Date: Sat, 01 Feb 2014 05:06:58 -0500 [thread overview]
Message-ID: <87vbwzi1tp.fsf@flea.lifelogs.com> (raw)
In-Reply-To: <87eh3ph5xu.fsf@nwalsh.com>
On Thu, 30 Jan 2014 08:58:53 -0600 Norman Walsh <ndw@nwalsh.com> wrote:
NW> Just FYI:
NW> Ted Zlatanov <tzz@lifelogs.com> writes:
NW> (setq gnus-registry-max-entries 20000
NW> gnus-registry-split-strategy nil
NW> gnus-registry-use-long-group-names t
NW> guns-registry-track-extra '(sender subject))
NW> First, note my clever spelling of "gnus" in
NW> "guns-registry-track-extra". That was fun to find.
>> You can set `gnus-verbose' to 9 and endure the noise until you catch the
>> problem. Sorry I don't have a better way.
NW> Yes, thanks. I finally got around to tracking this down. I added a new
NW> split rule that *never* worked and that made it a lot easier to debug.
NW> In this case, it turned out that gnus-registry-split-fancy-with-parent
NW> was splitting on subject and the subject was generic enough to have
NW> already been dropped in my "misc" bucket. Consequently, my new rule
NW> never fired.
NW> I expect that explains my other incorrect splits as well.
NW> I've removed "subject" from track-extra for the time being and I'll
NW> see how that goes. On the one hand, it was sometimes handy to have
NW> subject in the list, but I think the false splits probably outweigh
NW> that convenience.
I'm glad you found the problem. That misspelling is a tricky one.
Ted
prev parent reply other threads:[~2014-02-01 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 16:30 Norman Walsh
2013-12-10 17:07 ` Steinar Bang
2013-12-10 18:02 ` Norman Walsh
2013-12-13 14:22 ` Ted Zlatanov
2013-12-13 19:07 ` Norman Walsh
2014-01-30 14:58 ` Norman Walsh
2014-02-01 10:06 ` Ted Zlatanov [this message]
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=87vbwzi1tp.fsf@flea.lifelogs.com \
--to=tzz@lifelogs.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).