From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: message splitting gone haywire
Date: Thu, 29 Sep 2011 23:24:54 +0800 [thread overview]
Message-ID: <87oby3gym1.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87bou3jv8z.fsf@lifelogs.com>
On Thu, Sep 29 2011, Ted Zlatanov wrote:
> 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?
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
next prev parent reply other threads:[~2011-09-29 15:24 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
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 [this message]
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=87oby3gym1.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).