1 Return-Path: <felipe.contreras@gmail.com>
\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 203DF429E3E
\r
6 for <notmuch@notmuchmail.org>; Sun, 3 Nov 2013 12:10:46 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5
\r
12 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
\r
13 FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id XnGLvWltl+Ve for <notmuch@notmuchmail.org>;
\r
17 Sun, 3 Nov 2013 12:10:38 -0800 (PST)
\r
18 Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com
\r
19 [209.85.217.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
\r
20 (No client certificate requested)
\r
21 by olra.theworths.org (Postfix) with ESMTPS id 4F7F7429E38
\r
22 for <notmuch@notmuchmail.org>; Sun, 3 Nov 2013 12:10:38 -0800 (PST)
\r
23 Received: by mail-lb0-f181.google.com with SMTP id x18so4793635lbi.40
\r
24 for <notmuch@notmuchmail.org>; Sun, 03 Nov 2013 12:10:36 -0800 (PST)
\r
25 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
\r
26 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
\r
28 bh=NgtdF29Eg4XM6ylby9bZZm3VWFYJfPGbU31VD03U11Y=;
\r
29 b=rItyyX8ThBS5O/WpPPD7rDHXmfsBk5hJcZ8/g603D46UyoCMEPlDoIMlnNneS4svbf
\r
30 0heUSPmJF/3Cz3FegWzxvpbCrbWKxfvtq3NjBecrA82CXD5XzSHufm2yjAUmn3Jaa5d/
\r
31 cs1Z70Ov8p4jCkZ72fcdmYeGcblZFv3tvFU4lvqQojZDlofR8rQriK3Y+g4O+KwrtzQh
\r
32 T2jcip+tktMKMHS4pgctbGcXOhbI0QfLDD4pCuwqSFrTEwZJBWkAh/vEmmcIK44ToMNZ
\r
33 4EohZjPuS5xihnwRELOZdMntAdFfTlyESxu8WCkY3L5w4UfO82/VYw0c7Ur04yQzRU8w
\r
36 X-Received: by 10.112.29.147 with SMTP id k19mr8955295lbh.9.1383509434106;
\r
37 Sun, 03 Nov 2013 12:10:34 -0800 (PST)
\r
38 Received: by 10.114.201.69 with HTTP; Sun, 3 Nov 2013 12:10:33 -0800 (PST)
\r
39 In-Reply-To: <87wqkqono3.fsf@nikula.org>
\r
40 References: <5274f93e254b5_6de7f51e7849@nysa.notmuch>
\r
41 <87zjpmoqtz.fsf@nikula.org>
\r
42 <CAMP44s19GP0w9UTTzeos2wQXHuYLpfF74BdJpxvLy=RD16=HXg@mail.gmail.com>
\r
43 <87wqkqono3.fsf@nikula.org>
\r
44 Date: Sun, 3 Nov 2013 14:10:33 -0600
\r
46 <CAMP44s1aCWBFX1WdgTLZVcgKRdWLyi-npJqTcWeGHj+BrTpOWQ@mail.gmail.com>
\r
47 Subject: Re: Getting the right root mail of the thread
\r
48 From: Felipe Contreras <felipe.contreras@gmail.com>
\r
49 To: Jani Nikula <jani@nikula.org>
\r
50 Content-Type: text/plain; charset=UTF-8
\r
51 Cc: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
\r
52 X-BeenThere: notmuch@notmuchmail.org
\r
53 X-Mailman-Version: 2.1.13
\r
55 List-Id: "Use and development of the notmuch mail system."
\r
56 <notmuch.notmuchmail.org>
\r
57 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
58 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
59 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
60 List-Post: <mailto:notmuch@notmuchmail.org>
\r
61 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
62 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
63 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
64 X-List-Received-Date: Sun, 03 Nov 2013 20:10:46 -0000
\r
66 On Sat, Nov 2, 2013 at 8:58 AM, Jani Nikula <jani@nikula.org> wrote:
\r
67 > On Sat, 02 Nov 2013, Felipe Contreras <felipe.contreras@gmail.com> wrote:
\r
68 >> On Sat, Nov 2, 2013 at 7:50 AM, Jani Nikula <jani@nikula.org> wrote:
\r
69 >>> On Sat, 02 Nov 2013, Felipe Contreras <felipe.contreras@gmail.com> wrote:
\r
71 >>>> I think there should be a way to get the root mail of a thread,
\r
72 >>>> irrespective of the search order.
\r
74 >>> Largely agreed. It's just that nobody's gotten around to doing this
\r
75 >>> yet. At the cli level I think the consensus is that the structured
\r
76 >>> (sexp/json) output format should contain multiple (or all) subjects.
\r
78 >> What about the default? (--format=text). What about user-interfaces
\r
79 >> that must display a summary of a thread?
\r
81 > To be honest, we haven't had much interest in adding new content or
\r
82 > features to the text output formats. It's just much easier to do this in
\r
83 > a backwards compatible way in the structured output formats, for which
\r
84 > we also have the format versioning. The emacs ui uses the sexp format
\r
85 > for the thread summaries.
\r
87 How is this any better?
\r
89 (:thread "000000000000826a" :timestamp 1383396519 :date_relative
\r
90 "Yest. 06:48" :matched 45 :total 45 :authors "Felipe Contreras"
\r
91 :subject "[PATCH/TEST 44/44] request-pull: rewrite to C" :tags ("sent"
\r