Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: threading display strange
Date: Mon, 29 Apr 2019 08:53:15 +0200	[thread overview]
Message-ID: <871s1ljo9w.fsf@mat.ucm.es> (raw)
In-Reply-To: <87y33t9ywy.fsf@gnu.org>

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

>>> "TH" == Tassilo Horn <tsdh@gnu.org> writes:

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

>> I just realised that the following is odd:
>> 
>> []{ } 57606 [ Uwe Braue] Uwe Brauer [[CV] (was: [Amnu 19]) ] Sun, 28 Apr 2019
>> 11:30:41 +0200 8.8k 6
>> []{ }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
>> []{ } . 57604 [ Gestión d] oub@mat.uc [COMUNICADO AUTOMÁTICO DE ] Sun, 28 Apr
>> 2019 11:13:27 +0200 (CEST) 5.0k 32
>> []{ } 57608 [ Uwe Braue] Uwe Brauer [Re: [Amnu 19] ] Sun, 28 Apr 2019 11:31:33
>> +0200 11k ?
>> 
>> Why is  57606 displayed before  57585? 

> Well, since you didn't tell us how you've configured sorting, I assume
> you are using the defaults, and that would mean sorting by article
> number.

Sorry I posted my setting in a different message:

(setq gnus-thread-sort-functions
      '(gnus-thread-sort-by-date
        gnus-thread-sort-by-number))

(setq gnus-sort-functions
      '(gnus-article-sort-by-date
        gnus-article-sort-by-number))



> gnus-thread-sort-functions is a variable defined in ‘gnus-sum.el’.
> Its value is
> (...)
> Original value was 
> (gnus-thread-sort-by-number)

>   This variable may be risky if used as a file-local variable.

> Documentation:
> List of functions used for sorting threads in the summary buffer.
> By default, threads are sorted by article number.

> Each function takes two threads and returns non-nil if the first
> thread should be sorted before the other.  If you use more than one
> function, the primary sort function should be the last.  You should
> probably always include ‘gnus-thread-sort-by-number’ in the list of
> sorting functions -- preferably first.  Also note that sorting by date
> is often much slower than sorting by number, and the sorting order is
> very similar.  (Sorting by date means sorting by the time the message
> was sent, sorting by number means sorting by arrival time.)

> ...

> Especially, the last sentence might give a clue.  I think with NNTP
> (usegroups) the article number really exists on the server, so it's
> "time the message was received on that nntp server".  But with IMAP
> (mail) the number is assigned by Gnus, and then it basically gives the
> order in which you've downloaded the messages, and that's not really
> chronological.

Following your advice to read the documentation more carefully, I tried
the following setting

(setq gnus-thread-sort-functions
      '(gnus-thread-sort-by-number
        gnus-thread-sort-by-date))

(setq gnus-sort-functions
      '(gnus-article-sort-by-number
        gnus-article-sort-by-date))


However it does not help the summary buffer looks still
,----
| 
| []{ }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   
| []{ }O  57604 [  Gestión d] oub@mat.uc  [COMUNICADO AUTOMÁTICO DE ] Sun, 28 Apr 2019 11:13:27 +0200 (CEST) 5.0k 32   
| 
`----

So how could I achieve the following 

,----
| []{ }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  57604 [  Gestión d] oub@mat.uc  [COMUNICADO AUTOMÁTICO DE ] Sun, 28 Apr 2019 11:13:27 +0200 (CEST) 5.0k 32   
| []{ }O  57621 [  Uwe Braue] Uwe Brauer  [[stuff] (was: [CV])      ] Sun, 28 Apr 2019 16:04:34 +0200 9.4k 16   
`----

???

Because I have had sometimes difficult in finding message, but the
ordering I mentioned. So I had to toggle threading off to find them.

The setting I would like to obtain would spare me that trouble.

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]

  reply	other threads:[~2019-04-29  6:53 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 [this message]
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
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=871s1ljo9w.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).