From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: message splitting gone haywire
Date: Thu, 29 Sep 2011 03:38:42 -0500 [thread overview]
Message-ID: <877h4rn3ot.fsf@lifelogs.com> (raw)
In-Reply-To: <87ippv2phj.fsf@ericabrahamsen.net>
On Thu, 18 Aug 2011 14:38:48 +0800 Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
EA> I've been keeping up to date with git gnus (I'm on Ubuntu's 23.2 emacs),
EA> and a week or so ago, message splitting started going haywire. There's
EA> not much of a discernible pattern: messages are just going in the wrong
EA> groups.
EA> I'm using the registry, with gnus-registry-split-fancy-with-parent. Also
EA> BBDB 3.0, with bbdb/gnus-split method. Then some plain old
EA> nnmail-split-fancy regexps. None of these seems obviously the culprit.
EA> Some messages that should be split into their own groups by
EA> nnmail-split-fancy go into those groups half the time, into mail.misc
EA> the other half (they used to all go into the proper group, they're
EA> automated messages and neither the message nor the regexp has changed).
EA> A message I just sent from one of my email addresses to another of my
EA> email addresses went into a group that's only referenced by a
EA> gnus.private line in a BBDB record (not my own record, needless to say).
EA> Like I said, no one thing seems to be the clear source of the problem.
EA> Has anyone else seen anything like this over the past few weeks? I can
EA> paste the relevant part of my config, if necessary.
I didn't touch the registry around the time you mention. But I would
simply bisect the issue by limiting splitting to one method at a time
and see if it causes the aberrant behavior.
Ted
next prev parent reply other threads:[~2011-09-29 8:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 6:38 Eric Abrahamsen
2011-09-29 8:38 ` Ted Zlatanov [this message]
2011-09-29 9:00 ` Eric Abrahamsen
2011-09-29 12:47 ` Ted Zlatanov
2011-09-29 13:55 ` Eric Abrahamsen
2011-09-29 14:09 ` Ted Zlatanov
2011-09-29 15:24 ` Eric Abrahamsen
2011-09-29 18:49 ` Adam Sjøgren
2011-09-29 20:21 ` Ted Zlatanov
2011-09-29 20:38 ` Adam Sjøgren
2011-09-29 23:36 ` 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=877h4rn3ot.fsf@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).