1 Return-Path: <jrollins@finestructure.net>
\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 A7C064196F2
\r
6 for <notmuch@notmuchmail.org>; Mon, 21 Jun 2010 09:55:47 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-2.79 tagged_above=-999 required=5
\r
12 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_MED=-2.3, T_MIME_NO_TEXT=0.01]
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id sE3KvvPMzx0O for <notmuch@notmuchmail.org>;
\r
17 Mon, 21 Jun 2010 09:55:37 -0700 (PDT)
\r
18 Received: from brinza.cc.columbia.edu (brinza.cc.columbia.edu [128.59.29.8])
\r
19 by olra.theworths.org (Postfix) with ESMTP id 10D61431FC1
\r
20 for <notmuch@notmuchmail.org>; Mon, 21 Jun 2010 09:55:36 -0700 (PDT)
\r
21 Received: from servo.finestructure.net (rrcs-208-105-90-84.nyc.biz.rr.com
\r
23 (user=jgr2110 author=jrollins@finestructure.net mech=PLAIN bits=0)
\r
24 by brinza.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id o5LGtRJ0029129
\r
25 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT);
\r
26 Mon, 21 Jun 2010 12:55:28 -0400 (EDT)
\r
27 Received: from jrollins by servo.finestructure.net with local (Exim 4.72)
\r
28 (envelope-from <jrollins@finestructure.net>)
\r
29 id 1OQkHN-0004DJ-SO; Mon, 21 Jun 2010 12:55:25 -0400
\r
30 From: Jameson Rollins <jrollins@finestructure.net>
\r
31 To: Dirk Hohndel <hohndel@infradead.org>, notmuch <notmuch@notmuchmail.org>
\r
32 Subject: Re: thread sorting ideas
\r
33 In-Reply-To: <m339wg1ig3.fsf@x201s.gr8dns.org>
\r
34 References: <m339wg1ig3.fsf@x201s.gr8dns.org>
\r
35 User-Agent: Notmuch/0.3.1-59-g0b3b2bd (http://notmuchmail.org) Emacs/23.1.1
\r
37 Date: Mon, 21 Jun 2010 12:55:16 -0400
\r
38 Message-ID: <87ocf4nx57.fsf@servo.finestructure.net>
\r
40 Content-Type: multipart/signed; boundary="=-=-=";
\r
41 micalg=pgp-sha256; protocol="application/pgp-signature"
\r
42 X-No-Spam-Score: Local
\r
43 X-Scanned-By: MIMEDefang 2.68 on 128.59.29.8
\r
44 X-BeenThere: notmuch@notmuchmail.org
\r
45 X-Mailman-Version: 2.1.13
\r
47 List-Id: "Use and development of the notmuch mail system."
\r
48 <notmuch.notmuchmail.org>
\r
49 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
50 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
51 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
52 List-Post: <mailto:notmuch@notmuchmail.org>
\r
53 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
54 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
55 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
56 X-List-Received-Date: Mon, 21 Jun 2010 16:55:47 -0000
\r
59 Content-Transfer-Encoding: quoted-printable
\r
61 On Mon, 21 Jun 2010 09:03:40 -0700, Dirk Hohndel <hohndel@infradead.org> wr=
\r
63 > Here is a feature that I could really use some times...=20
\r
65 > Instead of sorting the threads based on the date of the first message in
\r
66 > the thread, sort them based on the newest message in the thread. So if I
\r
67 > take a quick look at the bottom (I am an "oldest first" kinda person) of
\r
68 > a search and I see all the threads that have the newest messages.
\r
70 > My suggestion would be to turn 'o' into a two key command:
\r
72 > o-o : oldest first, sort by oldest message in thread
\r
73 > o-O : oldest first, sort by newest message in thread
\r
74 > o-n : newest first, sort by oldest message in thread
\r
75 > o-N : newest first, sort by newest message in thread
\r
76 > o-s : sort by subject?
\r
77 > o-z : unthreaded, sort by message size?
\r
79 > you can come up with many more sort ideas...
\r
81 I too would really like to see threads sorted by the newest message in
\r
82 the thread when sorting oldest first. In fact, it seems to me that
\r
83 messages should *always* be sorted by the newest message in the thread.
\r
84 But I can accept that others might prefer different sortings, in which
\r
85 case your sorting suggestions seem abundantly reasonable to me, Dirk.
\r
90 Content-Type: application/pgp-signature
\r
92 -----BEGIN PGP SIGNATURE-----
\r
93 Version: GnuPG v1.4.10 (GNU/Linux)
\r
95 iQIcBAEBCAAGBQJMH5l2AAoJEO00zqvie6q8cXYQAJvWLNi2lYR1LxTP4Z0EfjOX
\r
96 kpfAEKY+rOwzUPW4vkzHaJHJ8meuyY6/bAEhevANQNsIHAb1AZTM6/BXkVFgsHQr
\r
97 cy4hPs4055BZXiBtVF0pwa145c8ZckfT7mFFsF48Vp2DiuijasuQz9weLq4+C0c+
\r
98 0FrxdH1sd8a2rkBXajeZFTC6rwatBqB5zy/HXq4Boq9Zf6xOz5UsGhcclvcYrVdS
\r
99 E00dmtg5C5GmciiLIZw9Fqbd60H3eiUrqjMuX4+cIHYF6f2w70h969gjZI7n+WPC
\r
100 s4dT05ddpaxU1Nx6omFBODF/VXAAP9x/Sdfy8/DAWHIqlHeJU5wpPS9vz3jDQTXr
\r
101 YUiFTaXkcr+uz0i8u/gt9i3t/2Iv4z0lGAWnmnCD1N1J9e36wHVzM/7ouBgfvZtE
\r
102 aaglRXx65Qw+WM5abMTV0sAmZTzRzjDjJQ2dJ1MKDnWFXX1tdo50uSTCcC8GecPt
\r
103 feioYjXu+gpg/CKk5Ydtq59fUMvvDwdHeV2KPzq5kmYJU1/tvLDHvulalCYUZxzl
\r
104 C5V/vr84euSGVGKyydlMEBrysV3dvuhSWPIXHH7uUYt9K7O5GEPxxbUPsWowQJUB
\r
105 9UzIUeaHqF+L19s4b80ckhSRaTadckIraW3GIFnz3+6AzA25UE48nrKLDr3YIZm/
\r
106 4hKvN2W9TFRdR/aNxrVx
\r
108 -----END PGP SIGNATURE-----
\r