1 Return-Path: <jani@nikula.org>
\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 982B2431FC3
\r
6 for <notmuch@notmuchmail.org>; Sat, 2 Nov 2013 06:50:43 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5
\r
12 tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id 6G7npVIhDr1I for <notmuch@notmuchmail.org>;
\r
16 Sat, 2 Nov 2013 06:50:38 -0700 (PDT)
\r
17 Received: from mail-ee0-f52.google.com (mail-ee0-f52.google.com
\r
18 [74.125.83.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client
\r
19 certificate requested) by olra.theworths.org (Postfix) with ESMTPS id
\r
20 E6DF3431FAF for <notmuch@notmuchmail.org>; Sat, 2 Nov 2013 06:50:37 -0700
\r
22 Received: by mail-ee0-f52.google.com with SMTP id e49so269122eek.25
\r
23 for <notmuch@notmuchmail.org>; Sat, 02 Nov 2013 06:50:36 -0700 (PDT)
\r
24 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
\r
25 d=1e100.net; s=20130820;
\r
26 h=x-gm-message-state:from:to:subject:in-reply-to:references
\r
27 :user-agent:date:message-id:mime-version:content-type;
\r
28 bh=881wPDXO5tG6yPT9Ok5giV+ktIf8eXPjKe2IRFkjZRc=;
\r
29 b=j1NUibys7BKagXvjcsVphW95dMBLpDVwv1yhWCLAC7/Y3fRCTpHMTe1tTkHWDxSCIQ
\r
30 W5BoGsklsOcUOXnpyU/M43LA0cTzRR+qsIyDWqYk5Yt4kihyao7KmJYFY5p8TCyCWiMv
\r
31 qaGZXIW6rI/tVvT4xjoVMihjlflEss8vxP2d9ZEYfyQevDc77DT6vRk8xBVz8C+Id4+T
\r
32 whtg+P/QMY8QhI2tgZeidVJCxhAN7mOu2L1sJrjy2RGbK5hwVu7LYLHho1FjYL6sm0er
\r
33 BlCUN3DSWzS9JQKwEYuj7w99s4wv1dccfcylsUWpJWPTr5dK89LhfEo8CP0E1HND1BJc
\r
36 ALoCoQlZzwIytw1VvTg5YHZQPTHXzgu4GRosu1ZuNYYzQ+jyWwMhnNQUKcvjErtgnhf7RvxOZAgB
\r
37 X-Received: by 10.15.98.9 with SMTP id bi9mr73195eeb.67.1383400235358;
\r
38 Sat, 02 Nov 2013 06:50:35 -0700 (PDT)
\r
39 Received: from localhost (dsl-hkibrasgw2-58c36f-91.dhcp.inet.fi.
\r
40 [88.195.111.91]) by mx.google.com with ESMTPSA id
\r
41 bn13sm20801753eeb.11.2013.11.02.06.50.33 for <multiple recipients>
\r
42 (version=TLSv1.2 cipher=RC4-SHA bits=128/128);
\r
43 Sat, 02 Nov 2013 06:50:34 -0700 (PDT)
\r
44 From: Jani Nikula <jani@nikula.org>
\r
45 To: Felipe Contreras <felipe.contreras@gmail.com>, notmuch@notmuchmail.org
\r
46 Subject: Re: Getting the right root mail of the thread
\r
47 In-Reply-To: <5274f93e254b5_6de7f51e7849@nysa.notmuch>
\r
48 References: <5274f93e254b5_6de7f51e7849@nysa.notmuch>
\r
49 User-Agent: Notmuch/0.16+106~g03cba67 (http://notmuchmail.org) Emacs/24.3.1
\r
50 (x86_64-pc-linux-gnu)
\r
51 Date: Sat, 02 Nov 2013 15:50:32 +0200
\r
52 Message-ID: <87zjpmoqtz.fsf@nikula.org>
\r
54 Content-Type: text/plain
\r
55 X-BeenThere: notmuch@notmuchmail.org
\r
56 X-Mailman-Version: 2.1.13
\r
58 List-Id: "Use and development of the notmuch mail system."
\r
59 <notmuch.notmuchmail.org>
\r
60 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
61 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
62 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
63 List-Post: <mailto:notmuch@notmuchmail.org>
\r
64 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
65 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
66 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
67 X-List-Received-Date: Sat, 02 Nov 2013 13:50:43 -0000
\r
69 On Sat, 02 Nov 2013, Felipe Contreras <felipe.contreras@gmail.com> wrote:
\r
70 > I often wondered why when browsing threads, I often see a message that doesn't
\r
71 > describe at all the thread, for example:
\r
73 > notmuch search ...
\r
74 > thread:000000000000826a 18 mins. ago [45/45] Felipe Contreras; [PATCH/TEST 44/44]
\r
76 > I can reverse the order of the search:
\r
78 > notmuch search --sort=oldest-first
\r
79 > thread:000000000000826a 23 mins. ago [45/45] Felipe Contreras; [PATCH/TEST 00/44]
\r
81 > Then I get the correct summary, but now the order of the search is the other
\r
82 > way around, and there doesn't seem to be a way to specify the order of the
\r
83 > messages independently of the order of the threads.
\r
85 I think it's actually worse than what your example demonstrates. It's
\r
86 the subject of the newest/oldest *matching* message that gets used. In
\r
87 your example, the first/last messages in the thread apparently match
\r
90 > Either way this doesn't make any sense to me. Each thread has a single origin
\r
91 > mail, why would anybody would like to show a message other than that while
\r
92 > displaying the summary of the tread? Even more, why isn't there an option to
\r
93 > fetch that information easily?
\r
95 > I am forced to get the list of messages, and then grab the first one, even
\r
96 > though it's not efficient, probably unnecessary, and potentiall wrong. For
\r
97 > example, it's possible that multiple mails arrived at the same time, then how
\r
98 > am I supposed to display the one that originated the thread?
\r
100 > I think there should be a way to get the root mail of a thread,
\r
101 > irrespective of the search order.
\r
103 Largely agreed. It's just that nobody's gotten around to doing this
\r
104 yet. At the cli level I think the consensus is that the structured
\r
105 (sexp/json) output format should contain multiple (or all) subjects.
\r