From: Uwe Brauer <email@example.com>
Subject: Re: summary buffer: wrong temporal order (permanent)
Date: Sat, 22 Oct 2022 21:46:31 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1709 bytes --]
>>> "AS" == Adam Sjøgren <email@example.com> writes:
> Uwe writes:
>> 3. However now, when I enter the INBOX in gnus the message are not
>> properly ordered with respect to their dates.
> For performance reasons, I think, Gnus defaults to sorting by number
> rather than date, so when you moved various emails out of INBOX and then
> back, the ordering got less close to "by date" than usual.
Ah, ok that makes sense
>> 4. gnus-summary-sort-by-date solves the issue, however only
>> temporary. So every time I quit gnus and open it again the
>> messages are not correctly ordered.
>> Anybody has an idea what to do?
> I thought you could configure your INBOX group to sort by date by
> setting gnus-article-sort-functions to 'gnus-article-sort-by-date in the
> group parameters, or globally, but I can't get it to work...
> Ah! That's because I have threading turned on - if you have that,
> gnus-thread-sort-functions is the variable you want to mess with.
> E.g. on INBOX you could press G p to edit the group parameters and then
> ((gnus-thread-sort-functions 'gnus-thread-sort-by-date))
Well I did both also
> Then press C-c C-c and Bob should be your uncle.
Well more likely Adam 😉
> Best regards,
Thanks and regards
Warning: Content may be disturbing to some audiences
I strongly condemn Putin's war of aggression against the Ukraine.
I support to deliver weapons to Ukraine's military.
I support the ban of Russia from SWIFT.
I support the EU membership of the Ukraine.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
prev parent reply other threads:[~2022-10-22 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 14:48 Uwe Brauer
2022-10-22 16:24 ` Adam Sjøgren
2022-10-22 19:46 ` Uwe Brauer [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).