Return-Path: <jani@nikula.org>
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 982B2431FC3
	for <notmuch@notmuchmail.org>; Sat,  2 Nov 2013 06:50:43 -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 6G7npVIhDr1I for <notmuch@notmuchmail.org>;
	Sat,  2 Nov 2013 06:50:38 -0700 (PDT)
Received: from mail-ee0-f52.google.com (mail-ee0-f52.google.com
 [74.125.83.52])	(using TLSv1 with cipher RC4-SHA (128/128 bits))	(No client
 certificate requested)	by olra.theworths.org (Postfix) with ESMTPS id
 E6DF3431FAF	for <notmuch@notmuchmail.org>; Sat,  2 Nov 2013 06:50:37 -0700
 (PDT)
Received: by mail-ee0-f52.google.com with SMTP id e49so269122eek.25
	for <notmuch@notmuchmail.org>; Sat, 02 Nov 2013 06:50:36 -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:subject:in-reply-to:references
	:user-agent:date:message-id:mime-version:content-type;
	bh=881wPDXO5tG6yPT9Ok5giV+ktIf8eXPjKe2IRFkjZRc=;
	b=j1NUibys7BKagXvjcsVphW95dMBLpDVwv1yhWCLAC7/Y3fRCTpHMTe1tTkHWDxSCIQ
	W5BoGsklsOcUOXnpyU/M43LA0cTzRR+qsIyDWqYk5Yt4kihyao7KmJYFY5p8TCyCWiMv
	qaGZXIW6rI/tVvT4xjoVMihjlflEss8vxP2d9ZEYfyQevDc77DT6vRk8xBVz8C+Id4+T
	whtg+P/QMY8QhI2tgZeidVJCxhAN7mOu2L1sJrjy2RGbK5hwVu7LYLHho1FjYL6sm0er
	BlCUN3DSWzS9JQKwEYuj7w99s4wv1dccfcylsUWpJWPTr5dK89LhfEo8CP0E1HND1BJc
	qaVA==
X-Gm-Message-State:
 ALoCoQlZzwIytw1VvTg5YHZQPTHXzgu4GRosu1ZuNYYzQ+jyWwMhnNQUKcvjErtgnhf7RvxOZAgB
X-Received: by 10.15.98.9 with SMTP id bi9mr73195eeb.67.1383400235358;
	Sat, 02 Nov 2013 06:50:35 -0700 (PDT)
Received: from localhost (dsl-hkibrasgw2-58c36f-91.dhcp.inet.fi.
	[88.195.111.91]) by mx.google.com with ESMTPSA id
	bn13sm20801753eeb.11.2013.11.02.06.50.33 for <multiple recipients>
	(version=TLSv1.2 cipher=RC4-SHA bits=128/128);
	Sat, 02 Nov 2013 06:50:34 -0700 (PDT)
From: Jani Nikula <jani@nikula.org>
To: Felipe Contreras <felipe.contreras@gmail.com>, notmuch@notmuchmail.org
Subject: Re: Getting the right root mail of the thread
In-Reply-To: <5274f93e254b5_6de7f51e7849@nysa.notmuch>
References: <5274f93e254b5_6de7f51e7849@nysa.notmuch>
User-Agent: Notmuch/0.16+106~g03cba67 (http://notmuchmail.org) Emacs/24.3.1
	(x86_64-pc-linux-gnu)
Date: Sat, 02 Nov 2013 15:50:32 +0200
Message-ID: <87zjpmoqtz.fsf@nikula.org>
MIME-Version: 1.0
Content-Type: text/plain
X-BeenThere: notmuch@notmuchmail.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: "Use and development of the notmuch mail system."
	<notmuch.notmuchmail.org>
List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
List-Archive: <http://notmuchmail.org/pipermail/notmuch>
List-Post: <mailto:notmuch@notmuchmail.org>
List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Nov 2013 13:50:43 -0000

On Sat, 02 Nov 2013, Felipe Contreras <felipe.contreras@gmail.com> wrote:
> I often wondered why when browsing threads, I often see a message that doesn't
> describe at all the thread, for example:
>
>   notmuch search ...
>   thread:000000000000826a 18 mins. ago [45/45] Felipe Contreras; [PATCH/TEST 44/44]
>
> I can reverse the order of the search:
>
>   notmuch search --sort=oldest-first
>   thread:000000000000826a 23 mins. ago [45/45] Felipe Contreras; [PATCH/TEST 00/44]
>
> Then I get the correct summary, but now the order of the search is the other
> way around, and there doesn't seem to be a way to specify the order of the
> messages independently of the order of the threads.

I think it's actually worse than what your example demonstrates. It's
the subject of the newest/oldest *matching* message that gets used. In
your example, the first/last messages in the thread apparently match
your query.

> Either way this doesn't make any sense to me. Each thread has a single origin
> mail, why would anybody would like to show a message other than that while
> displaying the summary of the tread? Even more, why isn't there an option to
> fetch that information easily?
>
> I am forced to get the list of messages, and then grab the first one, even
> though it's not efficient, probably unnecessary, and potentiall wrong. For
> example, it's possible that multiple mails arrived at the same time, then how
> am I supposed to display the one that originated the thread?
>
> 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.


BR,
Jani.