From: John Magolske <listmail@b79.net>
To: ding@gnus.org
Subject: Re: Sort recent threads towards bottom when gathering threads by subject?
Date: Thu, 16 Feb 2017 14:43:28 -0800 [thread overview]
Message-ID: <87k28pwycv.fsf@b79.net> (raw)
In-Reply-To: <87y3x738b5.fsf@linux-m68k.org>
Andreas Schwab <schwab@linux-m68k.org> writes:
> On Feb 14 2017, John Magolske <listmail@b79.net> wrote:
>
>> I can order threads how I'd like, but most recent messages & threads
>> with most recent message will be sorted towards the top like so:
>>
>> C (5 Feb 01:19)
>> A (2 Feb 13:49)
>> └─► A (4 Feb 20:05)
>> B (2 Feb 18:09)
>>
>> Here thread "A" is ahead of message "B" as the most recent message in
>> thread "A" is newer than "B". I'd like to have that sorting order, but
>> towards the bottom, and cannot figure out how to accomplish this.
>
> IIUC you can get what you want if you use
> `(not gnus-thread-sort-by-most-recent-number)'
> as the element of gnus-thread-sort-functions.
I have tried that...well, actually I was using this:
(setq gnus-thread-sort-functions
'((not gnus-thread-sort-by-most-recent-number)
(not gnus-thread-sort-by-most-recent-date)))
Per your suggestion I also tried:
(setq gnus-thread-sort-functions
'((not gnus-thread-sort-by-most-recent-number)))
In both cases this only gets the order I want (most recent message /
thread with most recent message ordered towards bottom) when gathering
threads by reference. When gathering threads by subject, messages are
ordered towards the bottom with sorting done by the root/oldest message
of threads rather than the most recent message. I'm still getting:
A (2 Feb 13:49)
└─► A (4 Feb 20:05)
B (2 Feb 18:09)
C (5 Feb 01:19)
I included various other threading-related settings in my previous post
thinking there might be some other factors contributing to this.
Thoughts?
John
--
John Magolske
http://b79.net/contact
next prev parent reply other threads:[~2017-02-16 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 23:17 John Magolske
2017-02-15 13:14 ` Andreas Schwab
2017-02-16 22:43 ` John Magolske [this message]
2017-04-07 23:47 ` John Magolske
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=87k28pwycv.fsf@b79.net \
--to=listmail@b79.net \
--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).