Re: notmuch-search-toggle-order and notmuch-tree

diff --git a/c0/cf99b3afb378ed564736dce17d37acd9971813 b/c0/cf99b3afb378ed564736dce17d37acd9971813
new file mode 100644 (file)
index 0000000..b03fbf4
--- /dev/null
+++ b/c0/cf99b3afb378ed564736dce17d37acd9971813
@@ -0,0 +1,64 @@
+Return-Path: <david@tethera.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 arlo.cworth.org (Postfix) with ESMTP id C88746DE8913\r
+ for <notmuch@notmuchmail.org>; Mon, 15 Aug 2016 05:11:32 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.007\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.007 tagged_above=-999 required=5 tests=[AWL=0.004,\r
+  SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id 679SRPG904Xn for <notmuch@notmuchmail.org>;\r
+ Mon, 15 Aug 2016 05:11:24 -0700 (PDT)\r
+Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id D75D66DEAA0E\r
+ for <notmuch@notmuchmail.org>; Mon, 15 Aug 2016 05:04:10 -0700 (PDT)\r
+Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2)\r
+ (envelope-from <david@tethera.net>)\r
+ id 1bZGcP-0006FF-Sr; Mon, 15 Aug 2016 08:03:49 -0400\r
+Received: (nullmailer pid 28202 invoked by uid 1000);\r
+ Mon, 15 Aug 2016 12:03:35 -0000\r
+From: David Bremner <david@tethera.net>\r
+To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,\r
+ notmuch@notmuchmail.org\r
+Subject: Re: notmuch-search-toggle-order and notmuch-tree\r
+In-Reply-To: <87zioj17bj.fsf@skywalker.in.ibm.com>\r
+References: <87zioj17bj.fsf@skywalker.in.ibm.com>\r
+User-Agent: Notmuch/0.22.1 (http://notmuchmail.org) Emacs/24.5.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Mon, 15 Aug 2016 09:03:35 -0300\r
+Message-ID: <878tvy8ciw.fsf@zancas.localnet>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.20\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <https://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: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Mon, 15 Aug 2016 12:11:33 -0000\r
+\r
+"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> writes:\r
+\r
+> I was expecting notmuch-tree to also follow the search\r
+> order(oldest-first or not). But with latest notmuch\r
+> even after i change the search order using notmuch-serach-toggle-order a\r
+> tree view always list with the default search order. Is that expected ?\r
+\r
+Maybe Mark can give a more informed comment but I would say that it's\r
+expected from a code point of view, as the tree code does not reference\r
+the variable notmuch-search-oldest-first. This lack of control over the\r
+display order of threads (as opposed to within the threads) does seem\r
+like a missing feature.\r
+\r
+d\r