From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: threading display strange
Date: Tue, 30 Apr 2019 09:37:46 +0200 [thread overview]
Message-ID: <871s1kymd1.fsf@mat.ucm.es> (raw)
In-Reply-To: <87h8ag9lal.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2494 bytes --]
>>> "TH" == Tassilo Horn <tsdh@gnu.org> writes:
> Uwe Brauer <oub@mat.ucm.es> writes:
>>> and they are not ordered monotonically. So which criterion do you
>>> actually want to use for sorting.
>>
>> Well if the date and time is too messy, I'd say I would like to sort by
>> number, but I want it montonically indepent whether threading is on or off
> I think, thus should be
> (setq gnus-thread-sort-functions '(gnus-thread-sort-by-number)
> gnus-article-sort-functions '(gnus-article-sort-by-number))
This was my first setting.
> then.
>> But it should be displayed as
>>
>> 57606 [ Uwe Braue] Uwe Brauer [[CV] (was: [Amnu 19]) ] Sun, 28 Apr 2019 11:30:41 +0200 8.8k 6
>> 57609 [ +henar de ] Uwe Brauer [ ] Sun, 28 Apr 2019 09:35:45 +0000 10k 13
>> 57585 [ tex-d-l-r] tex-d-l@li [tex-d-l Nachrichtenkompil] Sun, 28 Apr 2019 00:00:07 +0200 13k 165
>> 57593 [ users ] oub@mat.uc [Subject: Digest of users@] Sun, 28 Apr 2019 08:00:27 +0000 (UTC) 38k 11
>> 57621 [ Uwe Braue] Uwe Brauer [[stuff] (was: [CV]) ] Sun, 28 Apr 2019 16:04:34 +0200 9.4k 16
>>
>> That is what Thunderbird does and it looks more natural to me.
>> Did I explain clear enough what I want?
> Well, above you've said you want to sort by number and then you present
> an example which is not sorted by number... I don't know how thunderbird
> sorts, so I cannot come up with a "just like thunderbird" configuration.
Right, it should be
57585 [ tex-d-l-r] tex-d-l@li [tex-d-l Nachrichtenkompil] Sun, 28 Apr 2019 00:00:07 +0200 13k 165
57593 [ users ] oub@mat.uc [Subject: Digest of users@] Sun, 28 Apr 2019 08:00:27 +0000 (UTC) 38k 11
57606 [ Uwe Braue] Uwe Brauer [[CV] (was: [Amnu 19]) ] Sun, 28 Apr 2019 11:30:41 +0200 8.8k 6
57609 [ +henar de ] Uwe Brauer [ ] Sun, 28 Apr 2019 09:35:45 +0000 10k 13
57621 [ Uwe Braue] Uwe Brauer [[stuff] (was: [CV]) ] Sun, 28 Apr 2019 16:04:34 +0200 9.4k 16
My point being, that gnus does not sort it according to its own numbering.
> BTW, you can also re-sort the summary buffer interactively using the
> commands bound to the C-c C-s prefix. That's probably quicker to find a
> sorting version that suits your needs.
My feeling is, there is a bug in gnus, sort by numbers does not work,
when threading is on. Maybe later I send a bug report.
Thanks for your help
Uwe
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]
next prev parent reply other threads:[~2019-04-30 7:37 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
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 [this message]
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=871s1kymd1.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).