From: Michael Welsh Duggan <mwd@cert.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 18156@debbugs.gnu.org
Subject: bug#18156: Thread sorting before loose threads are gathered
Date: Thu, 26 Jan 2017 08:58:35 -0500 [thread overview]
Message-ID: <tnt60l16hys.fsf@lx-chumsalmon.ad.sei.cmu.edu> (raw)
In-Reply-To: <87o9yvov8c.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 25 Jan 2017 19:22:27 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Michael Welsh Duggan <mwd@md5i.com> writes:
>
>> Thread sorting happens before loose threads are gathered. See the
>> definition of `gnus-summary-prepare'. Threads are made, then cut, then
>> sorted, and then gathered. I believe they should be made, cut,
>> gathered, and then sorted. A consequence of the current order is that
>> using `gnus-thread-sort-by-most-recent-{number,date}' in the
>> `gnus-thread-sort-functions' will not pay attention to all messages in a
>> gathered thread.
>
> No, but you have `gnus-sort-gathered-threads-function' to sort inside
> the gathered threads, so I think the current algorithm is correct...
Correct or incorrect, it doesn't allow me to do what I want to do. Here
is my use case: I want to sort the threads in my summary buffer,
post-gathering, by the date of the most recent article in the thread.
If threads (not the articles in threads) are sorted before they are
gathered, this seems less than possible.
--
Michael Welsh Duggan
(mwd@cert.org)
next parent reply other threads:[~2017-01-26 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87a97qgzwk.fsf@maru2.md5i.com>
[not found] ` <87o9yvov8c.fsf@gnus.org>
2017-01-26 13:58 ` Michael Welsh Duggan [this message]
2017-01-26 14:19 ` bug#18156: Thread sorting before loose threads are gathered Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tnt60l16hys.fsf@lx-chumsalmon.ad.sei.cmu.edu \
--to=mwd@cert.org \
--cc=18156@debbugs.gnu.org \
--cc=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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).