From 14243ff630f8ccc95347ea0045cd8a9839c8d06c Mon Sep 17 00:00:00 2001 From: Jani Nikula Date: Sun, 3 Nov 2013 22:17:53 +0200 Subject: [PATCH] Re: Getting the right root mail of the thread --- 0d/b80fa8e558c0b4fca408ecf9fc35d9d37dbd8f | 112 ++++++++++++++++++++++ 1 file changed, 112 insertions(+) create mode 100644 0d/b80fa8e558c0b4fca408ecf9fc35d9d37dbd8f diff --git a/0d/b80fa8e558c0b4fca408ecf9fc35d9d37dbd8f b/0d/b80fa8e558c0b4fca408ecf9fc35d9d37dbd8f new file mode 100644 index 000000000..8082b5da3 --- /dev/null +++ b/0d/b80fa8e558c0b4fca408ecf9fc35d9d37dbd8f @@ -0,0 +1,112 @@ +Return-Path: +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by olra.theworths.org (Postfix) with ESMTP id 1C458429E43 + for ; Sun, 3 Nov 2013 12:18:04 -0800 (PST) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: -0.7 +X-Spam-Level: +X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 + tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled +Received: from olra.theworths.org ([127.0.0.1]) + by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id 05X+pgUYqfnq for ; + Sun, 3 Nov 2013 12:17:56 -0800 (PST) +Received: from mail-ea0-f177.google.com (mail-ea0-f177.google.com + [209.85.215.177]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id 826C9429E38 + for ; Sun, 3 Nov 2013 12:17:56 -0800 (PST) +Received: by mail-ea0-f177.google.com with SMTP id f15so2956725eak.8 + for ; Sun, 03 Nov 2013 12:17:55 -0800 (PST) +X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; + d=1e100.net; s=20130820; + h=x-gm-message-state:from:to:cc:subject:in-reply-to:references + :user-agent:date:message-id:mime-version:content-type; + bh=Na6cX7xtQHtdD53Hu0WCQAkKzZHn3+6csHbnRtWkcWc=; + b=R2aJds9X68vv0SOp6sPbnPQiibq09IX6XXEIYyHrwZpUMR6ka0P8aMBy9N9HA6LIn0 + rJrDrkBOs14laPS2MTvVMdN4LwIWKm9Pb0Lho/qd+uDD2G2VDwFzmuYJrZjPtXKpKd/U + XmSZwMP9ORiJ7VuJf6mnikyta16rT1B8DO3uhCrJCeTN/y9j0QDrbOUFAMcYFdW/4Qm2 + SWzYhrCsY6UKKgENIdcnja5CpYiq3fH0eu7suzHOOERME/qBctu4wqww2PDh8QkHNbK6 + proVrAAxVnBGBuoClrOJhQn2tobMiOSDoeKhtSwl7sGgB+xbbTmeRHoRUZ97WNIztQNK + IdmQ== +X-Gm-Message-State: + ALoCoQnyKbOZhYxmYO/TTGVhGCvSKrALHrcluhRhK5SUcaXvr+7Ndp+EyXiZS5JE0d/I9WqsOP+p +X-Received: by 10.15.101.13 with SMTP id bo13mr1202194eeb.77.1383509875212; + Sun, 03 Nov 2013 12:17:55 -0800 (PST) +Received: from localhost (dsl-hkibrasgw2-58c36f-91.dhcp.inet.fi. + [88.195.111.91]) + by mx.google.com with ESMTPSA id m54sm37403186eex.2.2013.11.03.12.17.53 + for + (version=TLSv1.2 cipher=RC4-SHA bits=128/128); + Sun, 03 Nov 2013 12:17:54 -0800 (PST) +From: Jani Nikula +To: Felipe Contreras +Subject: Re: Getting the right root mail of the thread +In-Reply-To: + +References: <5274f93e254b5_6de7f51e7849@nysa.notmuch> + <87zjpmoqtz.fsf@nikula.org> + + <87wqkqono3.fsf@nikula.org> + +User-Agent: Notmuch/0.16+120~gfd733a4 (http://notmuchmail.org) Emacs/24.3.1 + (x86_64-pc-linux-gnu) +Date: Sun, 03 Nov 2013 22:17:53 +0200 +Message-ID: <87mwllz1ce.fsf@nikula.org> +MIME-Version: 1.0 +Content-Type: text/plain +Cc: "notmuch@notmuchmail.org" +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.13 +Precedence: list +List-Id: "Use and development of the notmuch mail system." + +List-Unsubscribe: , + +List-Archive: +List-Post: +List-Help: +List-Subscribe: , + +X-List-Received-Date: Sun, 03 Nov 2013 20:18:04 -0000 + +On Sun, 03 Nov 2013, Felipe Contreras wrote: +> On Sat, Nov 2, 2013 at 8:58 AM, Jani Nikula wrote: +>> On Sat, 02 Nov 2013, Felipe Contreras wrote: +>>> On Sat, Nov 2, 2013 at 7:50 AM, Jani Nikula wrote: +>>>> On Sat, 02 Nov 2013, Felipe Contreras wrote: +>>> +>>>>> I think there should be a way to get the root mail of a thread, +>>>>> irrespective of the search order. +>>>> +>>>> Largely agreed. It's just that nobody's gotten around to doing this +>>>> yet. At the cli level I think the consensus is that the structured +>>>> (sexp/json) output format should contain multiple (or all) subjects. +>>> +>>> What about the default? (--format=text). What about user-interfaces +>>> that must display a summary of a thread? +>> +>> To be honest, we haven't had much interest in adding new content or +>> features to the text output formats. It's just much easier to do this in +>> a backwards compatible way in the structured output formats, for which +>> we also have the format versioning. The emacs ui uses the sexp format +>> for the thread summaries. +> +> How is this any better? +> +> (:thread "000000000000826a" :timestamp 1383396519 :date_relative +> "Yest. 06:48" :matched 45 :total 45 :authors "Felipe Contreras" +> :subject "[PATCH/TEST 44/44] request-pull: rewrite to C" :tags ("sent" +> "to-me")) + +I made no claims it would contain more or better information *now*. But +if someone were to add new things, the structured output is where it +would likely be added. We could add :subject_first, :subject_oldest, or +whatever *in addition* to :subject. + +BR, +Jani. + -- 2.26.2