From: Christoph Groth <christoph@grothesque.org>
To: info-gnus-english@gnu.org
Subject: Re: Reverse thread sorting by most recent number
Date: Thu, 19 Dec 2019 14:41:38 +0100 [thread overview]
Message-ID: <87o8w4a0vh.fsf@neron> (raw)
In-Reply-To: <871rt1tzjc.fsf@neron>
Christoph Groth wrote:
> I have set gnus-thread-sort-functions to
> '(gnus-thread-sort-by-most-recent-number) and this works as it should.
>
> Now I would like to reverse the sorting order so that the order of
> threads is consistent with the chronological order of messages within
> a thread.
I managed to solve the problem myself and reply here for reference. It
turns out that the threads that were sorted incorrectly were those with
missing messages.
For
(setq gnus-thread-sort-functions
'(gnus-thread-sort-by-number
(not gnus-thread-sort-by-most-recent-number)))
to work, i.e. for chronological sorting of threads according to the most
recent article, I also need to enable sparse threads:
(setq gnus-build-sparse-threads 'more)
Otherwise, the determination of the most recent number seems to be
hindered by missing articles. However, if
gnus-thread-sort-by-most-recent-number is not reversed, it seems to work
also without sparse threads.
After 20 years of using Gnus I'm still amazed how cool it is and how
arcane...
I guess that this problem would deserve being "fixed" in some way
(i.e. by clarifying documentation). Should I write to the emacs-devel
mailing list? Or is this issue not important enough?
Christoph
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
prev parent reply other threads:[~2019-12-19 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 15:37 Christoph Groth
2019-12-18 15:56 ` Fraga, Eric
2019-12-19 8:24 ` Christoph Groth
2019-12-19 13:41 ` Christoph Groth [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8w4a0vh.fsf@neron \
--to=christoph@grothesque.org \
--cc=info-gnus-english@gnu.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).