1 Return-Path: <sebastien.binet@cern.ch>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 34BC3431FB6
\r
6 for <notmuch@notmuchmail.org>; Wed, 9 Feb 2011 12:03:36 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0.01 tagged_above=-999 required=5
\r
12 tests=[T_MIME_NO_TEXT=0.01] autolearn=disabled
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id DfEc9mbzB+52 for <notmuch@notmuchmail.org>;
\r
16 Wed, 9 Feb 2011 12:03:34 -0800 (PST)
\r
17 Received: from CERNMX32.cern.ch (cernmx32.cern.ch [137.138.144.178])
\r
18 (using TLSv1 with cipher AES128-SHA (128/128 bits))
\r
19 (No client certificate requested)
\r
20 by olra.theworths.org (Postfix) with ESMTPS id 452DD431FB5
\r
21 for <notmuch@notmuchmail.org>; Wed, 9 Feb 2011 12:03:34 -0800 (PST)
\r
22 Received: from CERNFE20.cern.ch (137.138.144.155) by cernmxgwlb2.cern.ch
\r
23 (137.138.144.178) with Microsoft SMTP Server (TLS) id 14.1.270.1;
\r
24 Wed, 9 Feb 2011 21:03:31 +0100
\r
25 Received: from localhost (134.158.88.68) by smtp.cern.ch (137.138.144.172)
\r
26 with Microsoft SMTP Server (TLS) id 14.1.270.2; Wed, 9 Feb 2011 21:03:31
\r
28 From: Sebastien Binet <binet@cern.ch>
\r
29 To: Jesse Rosenthal <jrosenthal@jhu.edu>, Daniel Kahn Gillmor
\r
30 <dkg@fifthhorseman.net>, Jameson Rollins <jrollins@finestructure.net>
\r
31 Subject: Re: ordering threads by the latest message in a thread ?
\r
32 In-Reply-To: <m1pqr1rr6m.fsf@watt.hwcampus.jhu.edu>
\r
33 References: <87zkq5y2tq.fsf@cern.ch> <878vxp2ii5.fsf@servo.finestructure.net>
\r
34 <4D52DB62.5060604@fifthhorseman.net>
\r
35 <m1pqr1rr6m.fsf@watt.hwcampus.jhu.edu>
\r
36 User-Agent: Notmuch/0.5-63-g62725a5 (http://notmuchmail.org) Emacs/23.2.1
\r
37 (x86_64-unknown-linux-gnu)
\r
38 Date: Wed, 9 Feb 2011 21:03:06 +0100
\r
39 Message-ID: <87lj1px9fp.fsf@cern.ch>
\r
41 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1;
\r
42 protocol="application/pgp-signature"
\r
43 X-Originating-IP: [134.158.88.68]
\r
44 Keywords: CERN SpamKiller Note: -50
\r
45 Cc: notmuch@notmuchmail.org
\r
46 X-BeenThere: notmuch@notmuchmail.org
\r
47 X-Mailman-Version: 2.1.13
\r
49 List-Id: "Use and development of the notmuch mail system."
\r
50 <notmuch.notmuchmail.org>
\r
51 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
52 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
53 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
54 List-Post: <mailto:notmuch@notmuchmail.org>
\r
55 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
56 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
57 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
58 X-List-Received-Date: Wed, 09 Feb 2011 20:03:36 -0000
\r
61 Content-Transfer-Encoding: quoted-printable
\r
63 On Wed, 9 Feb 2011 13:36:17 -0500, Jesse Rosenthal <jrosenthal@jhu.edu> wro=
\r
66 > On Wed, 09 Feb 2011 13:22:26 -0500, Daniel Kahn Gillmor <dkg@fifthhorsema=
\r
69 > > Jameson, are you saying that "Search Oldest First" not only inverts the
\r
70 > > order of the threads, but also changes the a date a given thread is
\r
71 > > associated with?=20=20
\r
73 > The procedure is to match threads by either the oldest matching message
\r
74 > (in oldest first) or newest matching message (in newest first). So
\r
75 > matching newest first will make the thread with new messages go to the
\r
76 > top. But in oldest first -- which is what I imagine Sebastian was
\r
77 > looking at in the inbox -- the thread with an older inbox message will
\r
78 > appear further up.
\r
80 > So if Sebastian's message is tagged "inbox" this thread will appear,
\r
81 > under oldest-first, when he sent it; if it's not but Jamie's is, then it
\r
82 > will appear under Jamie's. But it'll appear under mine regardless in
\r
83 > newest first. I don't believe emacs has anything to do with it -- it's
\r
84 > how the nm binary orders threads as output to "search."
\r
87 I knew about the 'o' toggle that one could play with to display the
\r
88 threads, but I didn't notice this also modified how their ordering
\r
90 I naively thought it was just a matter of reverting the list.
\r
92 so, say I have the following messages and threads:
\r
93 id_0 1/3 [important meeting] - (received Monday)
\r
94 id_1 2/3 [important meeting] - (received Tuesday)
\r
95 id_2 1/1 [pick groceries] - (received Wednesday)
\r
96 id_3 3/3 [important meeting] - (received Thursday)
\r
97 id_4 1/1 [another title] - (received Friday morning)
\r
99 if I have 'Search Oldest first' "on", I'd get the following
\r
100 id_0 [and id_1 and id_3 folded in]
\r
104 and if it is "off":
\r
106 id_0 [and id_1 and id_3 folded in]
\r
109 but what I'd like to have is instead:
\r
111 id_0 [and id_1 and id_3 folded in]
\r
114 id_0 and friends come after id_2 because id_3 is more recent than id_2
\r
115 but older than id_4
\r
117 so: oldest first but only the latest of the messages of a thread to be
\r
118 considered for the thread-to-thread ordering.
\r
120 I prefer to process my emails like a stack growing from top to bottom ;)
\r
125 Content-Type: application/pgp-signature
\r
127 -----BEGIN PGP SIGNATURE-----
\r
128 Version: GnuPG v1.4.11 (GNU/Linux)
\r
130 iEYEARECAAYFAk1S8voACgkQPj4AVbsZCCZJVQCg9pTPskMycyKc32kJj84Tl+Co
\r
131 PJcAoMB0SkNyvFAaRUaTSUtG5Ak6jghi
\r
133 -----END PGP SIGNATURE-----
\r