Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: Correct ordering of items in mail threads
Date: Sun, 22 Oct 2023 09:29:15 -0700	[thread overview]
Message-ID: <871qdm62p0.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87lebumy5a.fsf@codeisgreat.org>

Pankaj Jangid <pankaj@codeisgreat.org> writes:

> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>> On Saturday, 21 Oct 2023 at 10:41, Pankaj Jangid wrote:
>>>  ;; Threading
>>>  '(gnus-thread-sort-functions
>>>    '(gnus-thread-sort-by-number))
>>>  '(gnus-summary-thread-gathering-function
>>>    'gnus-gather-threads-by-references)
>>>
>>
>> I have
>>
>> (setq gnus-sort-gathered-threads-function 'gnus-thread-sort-by-date)
>>
>> along with similar (but slightly different) settings for the variables
>> you've set.  This variable says how to sort *within* a thread which may
>> be what you are looking for.
>
> In fact, I wanted to use 'gnus-thread-sort-by-date for
> gnus-thread-sort-functions. But the docstring discouraged me.
>
> Also note that sorting by date is often much slower than sorting by
> number, and the sorting order is very similar.  (Sorting by date means
> sorting by the time the message was sent, sorting by number means
> sorting by arrival time.)

I think this is the trade-off, though -- sorting by number _usually_
means sorting by arrival time, but there's no contract there. It's
entirely possible for messages to arrive out-of-order, and when they do,
you get a weird display. I think a lot of what was slow in Gnus is
gradually becoming less slow (with things like native compilation and
whatnot) and you might try sorting by date and just seeing how bad it is.



  parent reply	other threads:[~2023-10-22 16:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-21  5:11 Pankaj Jangid
2023-10-22 11:24 ` Eric S Fraga
2023-10-22 16:15   ` Pankaj Jangid
2023-10-22 16:22     ` Adam Sjøgren
2023-10-22 16:29     ` Eric Abrahamsen [this message]
2023-10-22 16:53       ` Adam Sjøgren
2023-10-22 17:00         ` Eric Abrahamsen
2023-10-22 17:05           ` Adam Sjøgren
2023-10-22 17:11             ` Eric Abrahamsen
2023-10-23  7:39               ` Pankaj Jangid
2023-10-23 12:16                 ` Adam Sjøgren
2023-10-23 14:41                   ` Pankaj Jangid
2023-10-23 18:38                     ` Adam Sjøgren
2023-10-24  4:33                       ` Pankaj Jangid
2023-10-23 19:15                     ` Björn Bidar
     [not found]                     ` <1427.43186313368$1698088555@news.gmane.org>
2023-10-24  4:43                       ` Pankaj Jangid
2023-10-23 17:12                 ` Eric S Fraga
2023-10-24  4:28                   ` Pankaj Jangid
2023-10-24  6:14                     ` Eric S Fraga

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=871qdm62p0.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).