From: Jesse Rosenthal Date: Sun, 3 Nov 2013 20:35:59 +0000 (+1900) Subject: Re: Getting the right root mail of the thread X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=6f544dd6cfa032e048ceacdf0647846a97672e4e;p=notmuch-archives.git Re: Getting the right root mail of the thread --- diff --git a/8f/173e4b76c4d78e4580e2151a804a097db921fa b/8f/173e4b76c4d78e4580e2151a804a097db921fa new file mode 100644 index 000000000..fef177489 --- /dev/null +++ b/8f/173e4b76c4d78e4580e2151a804a097db921fa @@ -0,0 +1,82 @@ +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 25841429E43 + for ; Sun, 3 Nov 2013 13:36:30 -0800 (PST) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: 0 +X-Spam-Level: +X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] + 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 l82wFI1qyIdZ for ; + Sun, 3 Nov 2013 13:36:22 -0800 (PST) +X-Greylist: delayed 3602 seconds by postgrey-1.32 at olra; + Sun, 03 Nov 2013 13:36:22 PST +Received: from smtpauth.johnshopkins.edu (smtpauth.johnshopkins.edu + [162.129.8.201]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id 7BA3A429E38 + for ; Sun, 3 Nov 2013 13:36:22 -0800 (PST) +X-IronPort-AV: E=Sophos;i="4.93,627,1378872000"; d="scan'208";a="303075692" +Received: from c-69-137-43-192.hsd1.md.comcast.net (HELO lucky) + ([69.137.43.192]) + by ipex2.johnshopkins.edu with ESMTP/TLS/DHE-RSA-AES128-SHA; + 03 Nov 2013 15:36:18 -0500 +Received: from jkr by lucky with local (Exim 4.80) + (envelope-from ) + id 1Vd4Ot-00058J-IM; Sun, 03 Nov 2013 15:35:59 -0500 +From: Jesse Rosenthal +To: Jani Nikula , + Felipe Contreras , notmuch@notmuchmail.org +Subject: Re: Getting the right root mail of the thread +In-Reply-To: <87zjpmoqtz.fsf@nikula.org> +References: <5274f93e254b5_6de7f51e7849@nysa.notmuch> + <87zjpmoqtz.fsf@nikula.org> +User-Agent: Notmuch/0.16+119~g1eecfbd (http://notmuchmail.org) Emacs/24.1.1 + (i686-pc-linux-gnu) +Date: Sun, 03 Nov 2013 15:35:59 -0500 +Message-ID: <87k3gprzo0.fsf@jhu.edu> +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." + +List-Unsubscribe: , + +List-Archive: +List-Post: +List-Help: +List-Subscribe: , + +X-List-Received-Date: Sun, 03 Nov 2013 21:36:30 -0000 + +Jani Nikula writes: +> 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. + +The behavior is there because subjects frequently change in long +threads, and this allows the subject to refer to the most recent unread +message (if we're sorting in the default order). The +reason I requested and wrote in this behavior five years ago or so (my +only c contribution ever) was that numerous business associates would +keep email lists by replying and changing the subject. This is *very* +common outside of programming circles. Even in programming circles, +subjects frequently change on mailing list (with a "[was: ...]" +appended). + +The current behavior can be annoying, but the old behavior could make +the MUA quite unusable in a number of circumstances. (And yes, an MUA +that fails on reading mail from senders with bad emailing practices is +unusable for me.) + +Maybe there should be a "show original subject" toggle? That wouldn't be +too hard, though it would require another call to the library and +regenerating the search results.