Re: Getting the right root mail of the thread

diff --git a/ea/eca429fda3f3a5c924005ee9ec4d5c3c70bb05 b/ea/eca429fda3f3a5c924005ee9ec4d5c3c70bb05
new file mode 100644 (file)
index 0000000..75a9ae2
--- /dev/null
+++ b/ea/eca429fda3f3a5c924005ee9ec4d5c3c70bb05
@@ -0,0 +1,109 @@
+Return-Path: <jani@nikula.org>\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 982B2431FC3\r
+       for <notmuch@notmuchmail.org>; Sat,  2 Nov 2013 06:50:43 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_LOW=-0.7] 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 6G7npVIhDr1I for <notmuch@notmuchmail.org>;\r
+       Sat,  2 Nov 2013 06:50:38 -0700 (PDT)\r
+Received: from mail-ee0-f52.google.com (mail-ee0-f52.google.com\r
+ [74.125.83.52])       (using TLSv1 with cipher RC4-SHA (128/128 bits))        (No client\r
+ certificate requested)        by olra.theworths.org (Postfix) with ESMTPS id\r
+ E6DF3431FAF   for <notmuch@notmuchmail.org>; Sat,  2 Nov 2013 06:50:37 -0700\r
+ (PDT)\r
+Received: by mail-ee0-f52.google.com with SMTP id e49so269122eek.25\r
+       for <notmuch@notmuchmail.org>; Sat, 02 Nov 2013 06:50:36 -0700 (PDT)\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+       d=1e100.net; s=20130820;\r
+       h=x-gm-message-state:from:to:subject:in-reply-to:references\r
+       :user-agent:date:message-id:mime-version:content-type;\r
+       bh=881wPDXO5tG6yPT9Ok5giV+ktIf8eXPjKe2IRFkjZRc=;\r
+       b=j1NUibys7BKagXvjcsVphW95dMBLpDVwv1yhWCLAC7/Y3fRCTpHMTe1tTkHWDxSCIQ\r
+       W5BoGsklsOcUOXnpyU/M43LA0cTzRR+qsIyDWqYk5Yt4kihyao7KmJYFY5p8TCyCWiMv\r
+       qaGZXIW6rI/tVvT4xjoVMihjlflEss8vxP2d9ZEYfyQevDc77DT6vRk8xBVz8C+Id4+T\r
+       whtg+P/QMY8QhI2tgZeidVJCxhAN7mOu2L1sJrjy2RGbK5hwVu7LYLHho1FjYL6sm0er\r
+       BlCUN3DSWzS9JQKwEYuj7w99s4wv1dccfcylsUWpJWPTr5dK89LhfEo8CP0E1HND1BJc\r
+       qaVA==\r
+X-Gm-Message-State:\r
+ ALoCoQlZzwIytw1VvTg5YHZQPTHXzgu4GRosu1ZuNYYzQ+jyWwMhnNQUKcvjErtgnhf7RvxOZAgB\r
+X-Received: by 10.15.98.9 with SMTP id bi9mr73195eeb.67.1383400235358;\r
+       Sat, 02 Nov 2013 06:50:35 -0700 (PDT)\r
+Received: from localhost (dsl-hkibrasgw2-58c36f-91.dhcp.inet.fi.\r
+       [88.195.111.91]) by mx.google.com with ESMTPSA id\r
+       bn13sm20801753eeb.11.2013.11.02.06.50.33 for <multiple recipients>\r
+       (version=TLSv1.2 cipher=RC4-SHA bits=128/128);\r
+       Sat, 02 Nov 2013 06:50:34 -0700 (PDT)\r
+From: Jani Nikula <jani@nikula.org>\r
+To: Felipe Contreras <felipe.contreras@gmail.com>, notmuch@notmuchmail.org\r
+Subject: Re: Getting the right root mail of the thread\r
+In-Reply-To: <5274f93e254b5_6de7f51e7849@nysa.notmuch>\r
+References: <5274f93e254b5_6de7f51e7849@nysa.notmuch>\r
+User-Agent: Notmuch/0.16+106~g03cba67 (http://notmuchmail.org) Emacs/24.3.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Sat, 02 Nov 2013 15:50:32 +0200\r
+Message-ID: <87zjpmoqtz.fsf@nikula.org>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\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: Sat, 02 Nov 2013 13:50:43 -0000\r
+\r
+On Sat, 02 Nov 2013, Felipe Contreras <felipe.contreras@gmail.com> wrote:\r
+> I often wondered why when browsing threads, I often see a message that doesn't\r
+> describe at all the thread, for example:\r
+>\r
+>   notmuch search ...\r
+>   thread:000000000000826a 18 mins. ago [45/45] Felipe Contreras; [PATCH/TEST 44/44]\r
+>\r
+> I can reverse the order of the search:\r
+>\r
+>   notmuch search --sort=oldest-first\r
+>   thread:000000000000826a 23 mins. ago [45/45] Felipe Contreras; [PATCH/TEST 00/44]\r
+>\r
+> Then I get the correct summary, but now the order of the search is the other\r
+> way around, and there doesn't seem to be a way to specify the order of the\r
+> messages independently of the order of the threads.\r
+\r
+I think it's actually worse than what your example demonstrates. It's\r
+the subject of the newest/oldest *matching* message that gets used. In\r
+your example, the first/last messages in the thread apparently match\r
+your query.\r
+\r
+> Either way this doesn't make any sense to me. Each thread has a single origin\r
+> mail, why would anybody would like to show a message other than that while\r
+> displaying the summary of the tread? Even more, why isn't there an option to\r
+> fetch that information easily?\r
+>\r
+> I am forced to get the list of messages, and then grab the first one, even\r
+> though it's not efficient, probably unnecessary, and potentiall wrong. For\r
+> example, it's possible that multiple mails arrived at the same time, then how\r
+> am I supposed to display the one that originated the thread?\r
+>\r
+> I think there should be a way to get the root mail of a thread,\r
+> irrespective of the search order.\r
+\r
+Largely agreed. It's just that nobody's gotten around to doing this\r
+yet. At the cli level I think the consensus is that the structured\r
+(sexp/json) output format should contain multiple (or all) subjects.\r
+\r
+\r
+BR,\r
+Jani.\r