From: Jesse Rosenthal <jrosenthal@jhu.edu>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Jameson Rollins <jrollins@finestructure.net>
Cc: Sebastien Binet <binet@cern.ch>, notmuch@notmuchmail.org
Subject: Re: ordering threads by the latest message in a thread ?
Date: Wed, 09 Feb 2011 13:36:17 -0500 [thread overview]
Message-ID: <m1pqr1rr6m.fsf@watt.hwcampus.jhu.edu> (raw)
In-Reply-To: <4D52DB62.5060604@fifthhorseman.net>
On Wed, 09 Feb 2011 13:22:26 -0500, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
>
> Jameson, are you saying that "Search Oldest First" not only inverts the
> order of the threads, but also changes the a date a given thread is
> associated with?
The procedure is to match threads by either the oldest matching message
(in oldest first) or newest matching message (in newest first). So
matching newest first will make the thread with new messages go to the
top. But in oldest first -- which is what I imagine Sebastian was
looking at in the inbox -- the thread with an older inbox message will
appear further up.
So if Sebastian's message is tagged "inbox" this thread will appear,
under oldest-first, when he sent it; if it's not but Jamie's is, then it
will appear under Jamie's. But it'll appear under mine regardless in
newest first. I don't believe emacs has anything to do with it -- it's
how the nm binary orders threads as output to "search."
Apologies if this is restating what everyone already knew -- I couldn't
quite tell.
Best,
Jesse
next prev parent reply other threads:[~2011-02-09 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 9:28 ordering threads by the latest message in a thread ? Sebastien Binet
2011-02-09 18:02 ` Jameson Rollins
2011-02-09 18:22 ` Daniel Kahn Gillmor
2011-02-09 18:36 ` Jesse Rosenthal [this message]
2011-02-09 20:03 ` Sebastien Binet
2011-03-02 13:09 ` Xavier Maillard
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=m1pqr1rr6m.fsf@watt.hwcampus.jhu.edu \
--to=jrosenthal@jhu.edu \
--cc=binet@cern.ch \
--cc=dkg@fifthhorseman.net \
--cc=jrollins@finestructure.net \
--cc=notmuch@notmuchmail.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.
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).