ordering threads by the latest message in a thread ?

diff --git a/54/107f38d12cc8d682c6cae3b8b3a7a4d9073008 b/54/107f38d12cc8d682c6cae3b8b3a7a4d9073008
new file mode 100644 (file)
index 0000000..e4907be
--- /dev/null
+++ b/54/107f38d12cc8d682c6cae3b8b3a7a4d9073008
@@ -0,0 +1,88 @@
+Return-Path: <sebastien.binet@cern.ch>\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 F143C431FB6\r
+       for <notmuch@notmuchmail.org>; Wed,  9 Feb 2011 01:28:43 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.01\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.01 tagged_above=-999 required=5\r
+       tests=[T_MIME_NO_TEXT=0.01] autolearn=disabled\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 5TNebVksljP1 for <notmuch@notmuchmail.org>;\r
+       Wed,  9 Feb 2011 01:28:43 -0800 (PST)\r
+Received: from CERNMX32.cern.ch (cernmx32.cern.ch [137.138.144.178])\r
+       (using TLSv1 with cipher AES128-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 12B01431FB5\r
+       for <notmuch@notmuchmail.org>; Wed,  9 Feb 2011 01:28:43 -0800 (PST)\r
+Received: from CERNFE20.cern.ch (137.138.144.155) by cernmxgwlb2.cern.ch\r
+       (137.138.144.178) with Microsoft SMTP Server (TLS) id 14.1.270.1;\r
+       Wed, 9 Feb 2011 10:28:41 +0100\r
+Received: from localhost (134.158.88.68) by smtp.cern.ch (137.138.144.172)\r
+       with Microsoft SMTP Server (TLS) id 14.1.270.2; Wed, 9 Feb 2011 10:28:41\r
+       +0100\r
+From: Sebastien Binet <binet@cern.ch>\r
+To: <notmuch@notmuchmail.org>\r
+CC: \r
+Subject: ordering threads by the latest message in a thread ?\r
+User-Agent: Notmuch/0.5-63-g62725a5 (http://notmuchmail.org) Emacs/23.2.1\r
+       (x86_64-unknown-linux-gnu)\r
+Date: Wed, 9 Feb 2011 10:28:17 +0100\r
+Message-ID: <87zkq5y2tq.fsf@cern.ch>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1;\r
+       protocol="application/pgp-signature"\r
+X-Originating-IP: [134.158.88.68]\r
+Keywords: CERN SpamKiller Note: -50\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: Wed, 09 Feb 2011 09:28:44 -0000\r
+\r
+--=-=-=\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+\r
+hi there,\r
+\r
+right now, it seems like the messages are displayed and ordered in my\r
+inbox according to the date of the *first* message in a thread.\r
+\r
+that doesn't sound right to me as one can easily miss new replies to\r
+that thread (at least I did.)\r
+\r
+is there a way to modify this in the notmuch emacs interface so that\r
+threads are ordered according to the *latest* message in a thread\r
+instead ?\r
+(I am not fluent in lisp -- even if I am regularly trying to work on\r
+that specific issue -- so I might have missed an obvious way to perform\r
+such a thing.)\r
+\r
+=2D-=20\r
+@+\r
+=2Ds\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.11 (GNU/Linux)\r
+\r
+iEYEARECAAYFAk1SXjEACgkQPj4AVbsZCCaQbACdFTit3KEwYciq8YCqYWO/7CZn\r
+mqoAn2t8bp4MIZs6t6TUeXSQNSJERKmd\r
+=w7Nc\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r