Re: message splitting gone haywire

[Ted Zlatanov <tzz@lifelogs.com>]

On Thu, 29 Sep 2011 21:55:04 +0800 Eric Abrahamsen <eric@ericabrahamsen.net> wrote: 

EA> On Thu, Sep 29 2011, Ted Zlatanov wrote:
>> On Thu, 29 Sep 2011 17:00:16 +0800 Eric Abrahamsen <eric@ericabrahamsen.net> 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?

Either way they should be easy to implement, I just order the references
by age and then act as if the strategy was 'first.  But I just can't
think of a way to use 'oldest.

Ted