From: Ryan Tate <ryantate@ryantate.com>
To: David Bremner <david@tethera.net>
Cc: Tom Hirschowitz <tom.hirschowitz@univ-smb.fr>, notmuch@notmuchmail.org
Subject: Re: oldest-first
Date: Fri, 6 Mar 2020 11:50:18 -0500 [thread overview]
Message-ID: <FEFE72A3-25D5-44D7-BD41-69CE07FE143D@ryantate.com> (raw)
In-Reply-To: <87blp9cwnx.fsf@tethera.net>
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
> On Mar 6, 2020, at 10:47 AM, David Bremner <david@tethera.net> wrote:
>
> There is the following documentation in notmuch-search(1).
>
> Note: The thread order will be distinct between these two options (beyond being sim‐
> ply reversed). When sorting by oldest-first the threads will be sorted by the oldest
> message in each thread, but when sorting by newest-first the threads will be sorted
> by the newest message in each thread.
>
> If what you are seeing is consistent with that, then I guess it's
> officially not a bug.
The documentation seems to be in error, assuming you have copied it correctly. It says the thread orders are not strictly inverse between the two options, but then describes them precisely inverse.
Perhaps the word “unread” was unintentionally elided by the doc author, such that you could correct with the capitalized addition:
> When sorting by oldest-first the threads will be sorted by the oldest UNREAD
> message in each thread, but when sorting by newest-first the threads will be sorted
> by the newest message in each thread.
This would match the behavior described by Tom.
[-- Attachment #2: Type: text/html, Size: 2005 bytes --]
next prev parent reply other threads:[~2020-03-06 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 10:41 oldest-first Tom Hirschowitz
2020-03-06 15:47 ` oldest-first David Bremner
2020-03-06 16:46 ` oldest-first Tom Hirschowitz
2020-03-06 16:50 ` Ryan Tate [this message]
2020-03-06 16:53 ` oldest-first Ryan Tate
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FEFE72A3-25D5-44D7-BD41-69CE07FE143D@ryantate.com \
--to=ryantate@ryantate.com \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=tom.hirschowitz@univ-smb.fr \
/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 public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).