From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/80126 Path: news.gmane.org!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.gnus.general Subject: Re: message splitting gone haywire Date: Thu, 29 Sep 2011 23:24:54 +0800 Message-ID: <87oby3gym1.fsf@ericabrahamsen.net> References: <87ippv2phj.fsf@ericabrahamsen.net> <877h4rn3ot.fsf@lifelogs.com> <871uuziuzj.fsf@ericabrahamsen.net> <87sjnfjz1h.fsf@lifelogs.com> <87wrcrh2rr.fsf@ericabrahamsen.net> <87bou3jv8z.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1317309965 31325 80.91.229.12 (29 Sep 2011 15:26:05 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 29 Sep 2011 15:26:05 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M28420@lists.math.uh.edu Thu Sep 29 17:26:02 2011 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1R9IUs-0008BS-0V for ding-account@gmane.org; Thu, 29 Sep 2011 17:26:02 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1R9IUB-00087W-JG; Thu, 29 Sep 2011 10:25:19 -0500 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1R9IUA-00087I-Ar for ding@lists.math.uh.edu; Thu, 29 Sep 2011 10:25:18 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1R9IU5-00018B-CH for ding@lists.math.uh.edu; Thu, 29 Sep 2011 10:25:18 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1R9IU4-0000GM-0J for ding@gnus.org; Thu, 29 Sep 2011 17:25:12 +0200 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1R9IU3-0007kH-VA for ding@gnus.org; Thu, 29 Sep 2011 17:25:11 +0200 Original-Received: from 50-56-99-223.static.cloud-ips.com ([50.56.99.223]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Sep 2011 17:25:11 +0200 Original-Received: from eric by 50-56-99-223.static.cloud-ips.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Sep 2011 17:25:11 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 45 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 50-56-99-223.static.cloud-ips.com User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/23.2 (gnu/linux) Cancel-Lock: sha1:zIz98J0B86VsQkc9KrV6TtDrrzk= X-Spam-Score: -5.4 (-----) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:80126 Archived-At: On Thu, Sep 29 2011, Ted Zlatanov wrote: > On Thu, 29 Sep 2011 21:55:04 +0800 Eric Abrahamsen wrote: > > EA> On Thu, Sep 29 2011, Ted Zlatanov wrote: >>> On Thu, 29 Sep 2011 17:00:16 +0800 Eric Abrahamsen wrote: >>> > EA> I'm not sure what proper behavior should be, but I did expect that > EA> split-with-parent would send new messages to the location of the > EA> newest/nearest parent, and not to where some distant ancestor had once > EA> gone. >>> >>> Good point. Well, we build the full list of groups, then we call >>> `gnus-registry-post-process-groups' on it. That looks at >>> `gnus-registry-split-strategy' which is nil by default; the defcustom >>> says: >>> >>> '(choice :tag "Splitting strategy" >>> (const :tag "Only use single choices, discard multiple matches" nil) >>> (const :tag "Majority of matches wins" majority) >>> (const :tag "First found wins" first)) >>> >>> Have you customized this? My guess is you have 'first and the first >>> group in the list was from the oldest reference. > > EA> Huh, I set this to 'majority, probably early on when I had no idea how > EA> all this actually worked. That would indicate that I must have had more > EA> messages in the "wrong" group than in the "right", yes? It sure didn't > EA> seem that way at the time, though I could very well have been wrong. > EA> Anyway, now that I know how this actually works, it does seem that a > EA> 'newest and 'oldest would be handy. > > Yes, or there is a bug in my code ;) I should improve the logging in > that area. > > I get 'newest but I can't think of a reason for 'oldest. Can you? No I can't. The only time I wouldn't want 'newest is if I wanted to put one or two recent messages somewhere other than with their parents, but still wanted future messages to continue to be split with parents. This seems best served by 'majority (or a working version thereof :)). -- GNU Emacs 23.2.1 (i686-pc-linux-gnu, GTK+ Version 2.24.4) of 2011-04-04 on rothera, modified by DebiannNo Gnus v0.18