From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: threading display strange
Date: Mon, 29 Apr 2019 14:40:15 +0200 [thread overview]
Message-ID: <87k1fdassw.fsf@mat.ucm.es> (raw)
In-Reply-To: <87pnp59ild.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2777 bytes --]
>>> "TH" == Tassilo Horn <tsdh@gnu.org> writes:
> 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:
> gnus-thread-sort-functions is a variable defined in ‘gnus-sum.el’.
Thanks
I tried
(setq gnus-thread-sort-functions
'(not gnus-thread-sort-by-most-recent-date))
;; '(not gnus-thread-sort-by-date))
(setq gnus-sort-functions
'(not gnus-article-sort-by-most-recent-date))
;; '(not gnus-article-sort-by-date))
Or
(setq gnus-thread-sort-functions
'(not gnus-thread-sort-by-date))
(setq gnus-sort-functions
'(not gnus-article-sort-by-date))
But it does not work, for some strange reason gnus does not sort this
message according to its number or date. (But thunderbird does)
Here is a step to step description of how to obtain this (strange
behavior)
1. Set gnus-thread-ignore-subject to nil
2. Go to the last message in a given treat, answer it but change the
subject. Suppose you have Bcc or CC yourself
3. You answer will then be displayed as
[]{ }O 57606 [ Uwe Braue] Uwe Brauer [[CV] (was: [Amnu 19]) ] Sun, 28 Apr 2019 11:30:41 +0200 8.8k 6
[]{ }OA 57609 [ +henar de ] Uwe Brauer [ ] Sun, 28 Apr 2019 09:35:45 +0000 10k 13
[]{ }O 57621 [ Uwe Braue] Uwe Brauer [[stuff] (was: [CV]) ] Sun, 28 Apr 2019 16:04:34 +0200 9.4k 16
[]{ }O 57585 [ tex-d-l-r] tex-d-l@li [tex-d-l Nachrichtenkompil] Sun, 28 Apr 2019 00:00:07 +0200 13k 165
[]{ }O 57593 [ users ] oub@mat.uc [Subject: Digest of users@] Sun, 28 Apr 2019 08:00:27 +0000 (UTC) 38k 11
And not as it should be
[]{ }O 57606 [ Uwe Braue] Uwe Brauer [[CV] (was: [Amnu 19]) ] Sun, 28 Apr 2019 11:30:41 +0200 8.8k 6
[]{ }OA 57609 [ +henar de ] Uwe Brauer [ ] Sun, 28 Apr 2019 09:35:45 +0000 10k 13
[]{ }O 57585 [ tex-d-l-r] tex-d-l@li [tex-d-l Nachrichtenkompil] Sun, 28 Apr 2019 00:00:07 +0200 13k 165
[]{ }O 57593 [ users ] oub@mat.uc [Subject: Digest of users@] Sun, 28 Apr 2019 08:00:27 +0000 (UTC) 38k 11
[]{ }O 57621 [ Uwe Braue] Uwe Brauer [[stuff] (was: [CV]) ] Sun, 28 Apr 2019 16:04:34 +0200 9.4k 16
Could that be a bug?
Uwe
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]
next prev parent reply other threads:[~2019-04-29 12:40 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
2019-04-29 12:40 ` Uwe Brauer [this message]
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=87k1fdassw.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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).