From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: threading display strange
Date: Mon, 29 Apr 2019 22:55:53 +0200 [thread overview]
Message-ID: <87muk88rae.fsf@mat.ucm.es> (raw)
In-Reply-To: <87lfzsapiy.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 3769 bytes --]
> Uwe Brauer <oub@mat.ucm.es> writes:
> Those are all invalid. The variables' values must all be lists, and in
> order to negate an entry, you'd turn it into a list with car equal to
> not, e.g., it should be:
> (setq gnus-thread-sort-functions
> '((not gnus-thread-sort-by-number)
> (not gnus-thread-sort-by-most-recent-date)))
I tried that out, and it did not result in what I want
> Sorry, I don't see how the sorting is here. Converted to UTC, the times
> here are
> - 13:30:41
> - 09:35:45
> - 02:00:07
> - 08:00:27
> - 18:04:34
> 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
So again.
With threading on I see
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
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
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?
With treading off I see (when switching again to sort by numbers)
[]{ }O 57619 [ Uwe Braue] Uwe Brauer [Mail Archives ] Sun, 28 Apr 2019 15:46:43 +0200 0.7k 2
[]{ }O 57621 [ Uwe Braue] Uwe Brauer [[stuff] (was: [CV]) ] Sun, 28 Apr 2019 16:04:34 +0200 9.4k 16
[]{ }O 57622 [ Uwe Braue] JUAN JULIA [Re: Final de las clase ] Sun, 28 Apr 2019 16:11:26 +0200 8.7k 14
That is fine, just don't understand why gnus sorts:
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
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
> (setq gnus-thread-sort-functions '(gnus-thread-sort-by-number
> gnus-thread-sort-by-most-recent-date
> gnus-thread-sort-by-total-score)
> gnus-subthread-sort-functions '(gnus-thread-sort-by-number
> gnus-article-sort-by-date))
I tried that out did not work.
> This gives me high-score threads on top, and when the thread scores are
> equal, the thread with a newer message is above the other.
> Inside a thread, e.g., when there are multiple replies to the very same
> article, I sort chronologically with older above newer messages (so that
> I don't read the second reply before the first).
Right, I do the same
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]
next prev parent reply other threads:[~2019-04-29 20:55 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 [this message]
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=87muk88rae.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).