From 766a45e9527c841bdee39bce37f36891abfd12ea Mon Sep 17 00:00:00 2001 From: Jani Nikula Date: Sat, 2 Nov 2013 16:58:52 +0200 Subject: [PATCH] Re: Getting the right root mail of the thread --- e5/e771ada221e8fab8e8be7ce56e1f0388586080 | 101 ++++++++++++++++++++++ 1 file changed, 101 insertions(+) create mode 100644 e5/e771ada221e8fab8e8be7ce56e1f0388586080 diff --git a/e5/e771ada221e8fab8e8be7ce56e1f0388586080 b/e5/e771ada221e8fab8e8be7ce56e1f0388586080 new file mode 100644 index 000000000..db6aa7039 --- /dev/null +++ b/e5/e771ada221e8fab8e8be7ce56e1f0388586080 @@ -0,0 +1,101 @@ +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 EC025431FDB + for ; Sat, 2 Nov 2013 07:58:59 -0700 (PDT) +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 uSV83UVTTh3O for ; + Sat, 2 Nov 2013 07:58:55 -0700 (PDT) +Received: from mail-ee0-f48.google.com (mail-ee0-f48.google.com + [74.125.83.48]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client + certificate requested) by olra.theworths.org (Postfix) with ESMTPS id + 0D1D8431FD0 for ; Sat, 2 Nov 2013 07:58:54 -0700 + (PDT) +Received: by mail-ee0-f48.google.com with SMTP id d49so287730eek.21 + for ; Sat, 02 Nov 2013 07:58:53 -0700 (PDT) +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=kNIMKjI61ZSJdB8sL0tVCLdA6dSLq2uZOv2vR6U92IU=; + b=IDYNvyeoJOKrClrrg0HX5l7DNKj6hdoYUpHEVZApGh03FwNTFIzHaLJ278s3XLYMDb + iiy/AOGWAZmkoIJxj4wzJeN+SoNTPHj+Tjoo4T6rRfV3ppPJt8SZ4+3UhJu/tfPgpX3l + fSc3OloJRhplI915xkpSMFjnvgAWQHilJ6h4dYABTSgRRxkxN6MA29juHkM/E404v7EJ + B6Fa6stq/Sg2CvoOcszNsDkwkLvQ/S0eRAnq+jYScSCoPuXgju6yc9Oc//lfkTgQcA5c + XGvH7saoqe18C0v37LJWUuYSb6alTbnX06WDFoSb7uaOhOrcN7YicBaZGkvX0zEukLhg + 18ZA== +X-Gm-Message-State: + ALoCoQlKsdU9eMvzuVG4AAPzc8HC4t3uqKr3mIbUf/ivq/ruuJ8KZHCNo3g0slyHTcI444Bn51zY +X-Received: by 10.14.103.133 with SMTP id f5mr8122697eeg.48.1383404333798; + Sat, 02 Nov 2013 07:58:53 -0700 (PDT) +Received: from localhost (dsl-hkibrasgw2-58c36f-91.dhcp.inet.fi. + [88.195.111.91]) + by mx.google.com with ESMTPSA id a6sm21462985eei.10.2013.11.02.07.58.52 + for + (version=TLSv1.2 cipher=RC4-SHA bits=128/128); + Sat, 02 Nov 2013 07:58:53 -0700 (PDT) +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> + +User-Agent: Notmuch/0.16+106~g03cba67 (http://notmuchmail.org) Emacs/24.3.1 + (x86_64-pc-linux-gnu) +Date: Sat, 02 Nov 2013 16:58:52 +0200 +Message-ID: <87wqkqono3.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: Sat, 02 Nov 2013 14:59:00 -0000 + +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. + +That said, if someone were interested in amending notmuch search +--format=text --output=summary, I don't think we'd have anything against +it. I'd say a new option to specify a format string would be the way to +go. + + +BR, +Jani. -- 2.26.2