Re: thread sorting ideas

diff --git a/d2/5b46f6dcf260942064a5f43298473f5e662f0c b/d2/5b46f6dcf260942064a5f43298473f5e662f0c
new file mode 100644 (file)
index 0000000..ed2b4ff
--- /dev/null
+++ b/d2/5b46f6dcf260942064a5f43298473f5e662f0c
@@ -0,0 +1,109 @@
+Return-Path: <jrollins@finestructure.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id A7C064196F2\r
+       for <notmuch@notmuchmail.org>; Mon, 21 Jun 2010 09:55:47 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.79\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.79 tagged_above=-999 required=5\r
+       tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_MED=-2.3, T_MIME_NO_TEXT=0.01]\r
+       autolearn=ham\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id sE3KvvPMzx0O for <notmuch@notmuchmail.org>;\r
+       Mon, 21 Jun 2010 09:55:37 -0700 (PDT)\r
+Received: from brinza.cc.columbia.edu (brinza.cc.columbia.edu [128.59.29.8])\r
+       by olra.theworths.org (Postfix) with ESMTP id 10D61431FC1\r
+       for <notmuch@notmuchmail.org>; Mon, 21 Jun 2010 09:55:36 -0700 (PDT)\r
+Received: from servo.finestructure.net (rrcs-208-105-90-84.nyc.biz.rr.com\r
+       [208.105.90.84])\r
+       (user=jgr2110 author=jrollins@finestructure.net mech=PLAIN bits=0)\r
+       by brinza.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id o5LGtRJ0029129\r
+       (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT);\r
+       Mon, 21 Jun 2010 12:55:28 -0400 (EDT)\r
+Received: from jrollins by servo.finestructure.net with local (Exim 4.72)\r
+       (envelope-from <jrollins@finestructure.net>)\r
+       id 1OQkHN-0004DJ-SO; Mon, 21 Jun 2010 12:55:25 -0400\r
+From: Jameson Rollins <jrollins@finestructure.net>\r
+To: Dirk Hohndel <hohndel@infradead.org>, notmuch <notmuch@notmuchmail.org>\r
+Subject: Re: thread sorting ideas\r
+In-Reply-To: <m339wg1ig3.fsf@x201s.gr8dns.org>\r
+References: <m339wg1ig3.fsf@x201s.gr8dns.org>\r
+User-Agent: Notmuch/0.3.1-59-g0b3b2bd (http://notmuchmail.org) Emacs/23.1.1\r
+       (i486-pc-linux-gnu)\r
+Date: Mon, 21 Jun 2010 12:55:16 -0400\r
+Message-ID: <87ocf4nx57.fsf@servo.finestructure.net>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+       micalg=pgp-sha256; protocol="application/pgp-signature"\r
+X-No-Spam-Score: Local\r
+X-Scanned-By: MIMEDefang 2.68 on 128.59.29.8\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Mon, 21 Jun 2010 16:55:47 -0000\r
+\r
+--=-=-=\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+On Mon, 21 Jun 2010 09:03:40 -0700, Dirk Hohndel <hohndel@infradead.org> wr=\r
+ote:\r
+> Here is a feature that I could really use some times...=20\r
+>=20\r
+> Instead of sorting the threads based on the date of the first message in\r
+> the thread, sort them based on the newest message in the thread. So if I\r
+> take a quick look at the bottom (I am an "oldest first" kinda person) of\r
+> a search and I see all the threads that have the newest messages.\r
+>=20\r
+> My suggestion would be to turn 'o' into a two key command:\r
+>=20\r
+> o-o : oldest first, sort by oldest message in thread\r
+> o-O : oldest first, sort by newest message in thread\r
+> o-n : newest first, sort by oldest message in thread\r
+> o-N : newest first, sort by newest message in thread\r
+> o-s : sort by subject?\r
+> o-z : unthreaded, sort by message size?\r
+>=20\r
+> you can come up with many more sort ideas...\r
+\r
+I too would really like to see threads sorted by the newest message in\r
+the thread when sorting oldest first.  In fact, it seems to me that\r
+messages should *always* be sorted by the newest message in the thread.\r
+But I can accept that others might prefer different sortings, in which\r
+case your sorting suggestions seem abundantly reasonable to me, Dirk.\r
+\r
+jamie.\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.10 (GNU/Linux)\r
+\r
+iQIcBAEBCAAGBQJMH5l2AAoJEO00zqvie6q8cXYQAJvWLNi2lYR1LxTP4Z0EfjOX\r
+kpfAEKY+rOwzUPW4vkzHaJHJ8meuyY6/bAEhevANQNsIHAb1AZTM6/BXkVFgsHQr\r
+cy4hPs4055BZXiBtVF0pwa145c8ZckfT7mFFsF48Vp2DiuijasuQz9weLq4+C0c+\r
+0FrxdH1sd8a2rkBXajeZFTC6rwatBqB5zy/HXq4Boq9Zf6xOz5UsGhcclvcYrVdS\r
+E00dmtg5C5GmciiLIZw9Fqbd60H3eiUrqjMuX4+cIHYF6f2w70h969gjZI7n+WPC\r
+s4dT05ddpaxU1Nx6omFBODF/VXAAP9x/Sdfy8/DAWHIqlHeJU5wpPS9vz3jDQTXr\r
+YUiFTaXkcr+uz0i8u/gt9i3t/2Iv4z0lGAWnmnCD1N1J9e36wHVzM/7ouBgfvZtE\r
+aaglRXx65Qw+WM5abMTV0sAmZTzRzjDjJQ2dJ1MKDnWFXX1tdo50uSTCcC8GecPt\r
+feioYjXu+gpg/CKk5Ydtq59fUMvvDwdHeV2KPzq5kmYJU1/tvLDHvulalCYUZxzl\r
+C5V/vr84euSGVGKyydlMEBrysV3dvuhSWPIXHH7uUYt9K7O5GEPxxbUPsWowQJUB\r
+9UzIUeaHqF+L19s4b80ckhSRaTadckIraW3GIFnz3+6AzA25UE48nrKLDr3YIZm/\r
+4hKvN2W9TFRdR/aNxrVx\r
+=2WqB\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r