all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: "Michael Welsh Duggan" <mwd@md5i.com>,
	"Emilia Blåsten" <emilia.blasten@iki.fi>,
	53755@debbugs.gnu.org
Subject: bug#53755: 27.2; C-u M-x gnus-summary-sort-by-most-recent-number / -date not ordering threads as expected
Date: Mon, 07 Feb 2022 01:03:50 +0100	[thread overview]
Message-ID: <87sfsv35ll.fsf@gnus.org> (raw)
In-Reply-To: <874k5dcsgf.fsf@gmail.com> ("Kévin Le Gouguec"'s message of "Sat, 05 Feb 2022 15:13:04 +0100")

Kévin Le Gouguec <kevin.legouguec@gmail.com> writes:

> Now that Michael has blessed us with a patch, I guess I could live with
> keeping it applied locally, but I really wonder how useful the current
> semantics of gnus-thread-sort-by-most-recent-date are… since… threads
> don't end up sorted by date 🙃

We could apply Michael's patch, but it needs a user option to switch
between the two behaviours, and for it to be generally useful, it needs
all those different sorting functions I mentioned in that other bug
report, I think...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-02-07  0:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 18:37 bug#53755: 27.2; C-u M-x gnus-summary-sort-by-most-recent-number / -date not ordering threads as expected Emilia Blåsten
2022-02-03 19:15 ` Lars Ingebrigtsen
2022-02-03 19:54 ` Arash Esbati
2022-02-03 22:18 ` Michael Welsh Duggan
2022-02-03 23:30   ` Kévin Le Gouguec
2022-02-04  3:33     ` Michael Welsh Duggan
2022-02-04 23:11       ` Emilia Blåsten
2022-02-05 14:13         ` Kévin Le Gouguec
2022-02-07  0:03           ` Lars Ingebrigtsen [this message]
2022-02-07  2:35             ` Michael Welsh Duggan

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=87sfsv35ll.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=53755@debbugs.gnu.org \
    --cc=emilia.blasten@iki.fi \
    --cc=kevin.legouguec@gmail.com \
    --cc=mwd@md5i.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.