From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: different thread sorting?
Date: 07 Nov 1998 15:10:34 +0100 [thread overview]
Message-ID: <m3zpa3r3tx.fsf@sparky.gnus.org> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "02 Nov 1998 17:19:04 +0100"
Kai.Grossjohann@CS.Uni-Dortmund.DE writes:
> Current behavior:
> Thread A is sorted before thread B if the OLDEST article in A is older
> than the OLDEST article in B.
That's almost right -- the threads are sorted on the thread root.
This is the oldest article in most cases, but in some weird cases,
it's not.
> Desired behavior:
> Thread A is sorted before thread B if the NEWEST article in A is older
> than the NEWEST article in B.
>
> Of course, this behavior should be optional.
>
> What has become of this issue?
I haven't done anything about it. Implementing it shouldn't be too
difficult, I think -- one should write a function that descends the
thread tree and returns the header of the newest article, and then just
sort the threads using a function that would look like:
(defun gnus-thread-sort-by-newest-date (h1 h2)
"Sort threads by root article date."
(gnus-article-sort-by-date
(gnus-newest-article-in-thread h1) (gnus-newest-article-in-thread h2)))
Writing `gnus-newest-article-in-thread' is left as an exercise for the
reader.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-11-07 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-02 16:19 Kai.Grossjohann
1998-11-07 14:10 ` Lars Magne Ingebrigtsen [this message]
1998-11-09 16:38 ` Wes Hardaker
1998-11-10 4:51 ` Lars Magne Ingebrigtsen
1998-11-10 17:25 ` Wes Hardaker
1998-11-13 18:08 ` Lars Magne Ingebrigtsen
1998-11-13 18:43 ` Wes Hardaker
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=m3zpa3r3tx.fsf@sparky.gnus.org \
--to=larsi@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).