GNU bug report logs -
#42334
28.0.50; gnus-thread-sort-functions vs. loose threads
Previous Next
Reported by: Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
Date: Sun, 12 Jul 2020 13:07:01 UTC
Severity: normal
Tags: wontfix
Found in version 28.0.50
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
Message #18 received at 42334 <at> debbugs.gnu.org (full text, mbox):
Kévin Le Gouguec <kevin.legouguec <at> gmail.com> writes:
> Understood. It's not too annoying when reading news since I rarely have
> more than a screenful of summary for any given group, but it can get
> confusing when looking at archives: a recently updated subthread can be
> hidden several screens up because a sibling subthread is too old…
>
> I'll file this one under "don't hack on this unless I can spend a couple
> of days on it". Thanks a lot for taking the time to pinpoint where the
> issue lies, that's really helpful!
It would be nice. The thing is that it requires writing new versions of
all these functions:
(choice (function-item gnus-thread-sort-by-number)
(function-item gnus-thread-sort-by-author)
(function-item gnus-thread-sort-by-recipient)
(function-item gnus-thread-sort-by-subject)
(function-item gnus-thread-sort-by-date)
(function-item gnus-thread-sort-by-score)
(function-item gnus-thread-sort-by-most-recent-number)
(function-item gnus-thread-sort-by-most-recent-date)
(function-item gnus-thread-sort-by-random)
(function-item gnus-thread-sort-by-total-score)
The new versions would take gathered threads as the parameters instead
of real threads. (Gathered threads are just lists of real threads, so
it's pretty straightforward.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
This bug report was last modified 5 years and 28 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.