Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: ding@gnus.org
Subject: Re: threading display strange
Date: Mon, 29 Apr 2019 13:06:06 +0200	[thread overview]
Message-ID: <87pnp59ild.fsf@gnu.org> (raw)
In-Reply-To: <87ftq1hzsu.fsf@mat.ucm.es> (Uwe Brauer's message of "Mon, 29 Apr 2019 12:27:13 +0200")

[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]

Uwe Brauer <oub@mat.ucm.es> writes:

>> I guess you want gnus-thread-sort-by-most-recent-date and
>> gnus-article-sort-by-most-recent-date because gnus-thread-sort-by-date
>> sorts by the date of the root article.
>
> This is what I thought, but then the summary buffer displays the most
> recent dates first and the beginning of the buffer, which is not what I
> want as in 
>
> @ Start of buffer
> ...
> So this is not what I want:
> I want the most recent message at the end of the buffer not at the
> beginning

Then negate the sorting functions:

--8<---------------cut here---------------start------------->8---
gnus-thread-sort-functions is a variable defined in ‘gnus-sum.el’.

...

Documentation:
...

Each list item can also be a list ‘(not F)’ where F is a
function; this specifies reversed sort order.
--8<---------------cut here---------------end--------------->8---

BTW, there's also gnus-subthread-sort-functions which would allow you
to, e.g., have threads with the newest articles on top while still have
subthreads sorted chronologically from top (older) to bottom (newer).

Bye,
Tassilo

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2019-04-29 11:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-28  9:34 Uwe Brauer
2019-04-29  5:13 ` Tassilo Horn
2019-04-29  6:53   ` Uwe Brauer
2019-04-29  9:26     ` Tassilo Horn
2019-04-29 10:27       ` Uwe Brauer
2019-04-29 11:06         ` Tassilo Horn [this message]
2019-04-29 12:40           ` Uwe Brauer
2019-04-29 13:51             ` Tassilo Horn
2019-04-29 20:55               ` Uwe Brauer
2019-04-30  4:20                 ` Tassilo Horn
2019-04-30  7:37                   ` Uwe Brauer
2019-04-30  8:32                     ` Tassilo Horn
2019-04-30 10:51                       ` Uwe Brauer

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=87pnp59ild.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --cc=ding@gnus.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).