From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: 42334@debbugs.gnu.org
Subject: bug#42334: 28.0.50; gnus-thread-sort-functions vs. loose threads
Date: Sun, 19 Jul 2020 15:09:13 +0200 [thread overview]
Message-ID: <87ft9nslc6.fsf@gnus.org> (raw)
In-Reply-To: <87mu3vq1re.fsf@gmail.com> ("Kévin Le Gouguec"'s message of "Sun, 19 Jul 2020 11:42:45 +0200")
Kévin Le Gouguec <kevin.legouguec@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
prev parent reply other threads:[~2020-07-19 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-12 13:05 bug#42334: 28.0.50; gnus-thread-sort-functions vs. loose threads Kévin Le Gouguec
2020-07-19 0:13 ` Lars Ingebrigtsen
2020-07-19 9:42 ` Kévin Le Gouguec
2020-07-19 13:09 ` Lars Ingebrigtsen [this message]
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=87ft9nslc6.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=42334@debbugs.gnu.org \
--cc=kevin.legouguec@gmail.com \
/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).