Re: Provide an option to make thread summaries keep initial subject
authorAustin Clements <amdragon@MIT.EDU>
Tue, 25 Sep 2012 19:31:37 +0000 (15:31 +2000)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 17:49:37 +0000 (09:49 -0800)
2c/321c2e42e72bf4d12ac46ada76625220dd216c [new file with mode: 0644]

diff --git a/2c/321c2e42e72bf4d12ac46ada76625220dd216c b/2c/321c2e42e72bf4d12ac46ada76625220dd216c
new file mode 100644 (file)
index 0000000..07aca23
--- /dev/null
@@ -0,0 +1,110 @@
+Return-Path: <amdragon@mit.edu>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 6FC50431FC4\r
+       for <notmuch@notmuchmail.org>; Tue, 25 Sep 2012 12:31:42 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id Ubto8pQMBQSC for <notmuch@notmuchmail.org>;\r
+       Tue, 25 Sep 2012 12:31:42 -0700 (PDT)\r
+Received: from dmz-mailsec-scanner-7.mit.edu (DMZ-MAILSEC-SCANNER-7.MIT.EDU\r
+       [18.7.68.36])\r
+       by olra.theworths.org (Postfix) with ESMTP id D7729431FAF\r
+       for <notmuch@notmuchmail.org>; Tue, 25 Sep 2012 12:31:41 -0700 (PDT)\r
+X-AuditID: 12074424-b7fce6d000000925-dd-5062069d9b98\r
+Received: from mailhub-auth-4.mit.edu ( [18.7.62.39])\r
+       by dmz-mailsec-scanner-7.mit.edu (Symantec Messaging Gateway) with SMTP\r
+       id A5.4E.02341.D9602605; Tue, 25 Sep 2012 15:31:41 -0400 (EDT)\r
+Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])\r
+       by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id q8PJVefs020143; \r
+       Tue, 25 Sep 2012 15:31:40 -0400\r
+Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91])\r
+       (authenticated bits=0)\r
+       (User authenticated as amdragon@ATHENA.MIT.EDU)\r
+       by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id q8PJVbDu001553\r
+       (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT);\r
+       Tue, 25 Sep 2012 15:31:39 -0400 (EDT)\r
+Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.77)\r
+       (envelope-from <amdragon@mit.edu>)\r
+       id 1TGar3-0008Nw-An; Tue, 25 Sep 2012 15:31:37 -0400\r
+Date: Tue, 25 Sep 2012 15:31:37 -0400\r
+From: Austin Clements <amdragon@MIT.EDU>\r
+To: Olivier Berger <olivier.berger@it-sudparis.eu>\r
+Subject: Re: Provide an option to make thread summaries keep initial subject\r
+Message-ID: <20120925193137.GM26662@mit.edu>\r
+References: <87zk4eqech.fsf@inf-8657.int-evry.fr>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+Content-Disposition: inline\r
+In-Reply-To: <87zk4eqech.fsf@inf-8657.int-evry.fr>\r
+User-Agent: Mutt/1.5.21 (2010-09-15)\r
+X-Brightmail-Tracker:\r
+ H4sIAAAAAAAAA+NgFmpileLIzCtJLcpLzFFi42IRYrdT153LlhRgcPqPuMX1mzOZLRrPtLM5\r
+       MHk8advE4vFs1S3mAKYoLpuU1JzMstQifbsEroz3TR0sBQt5K+bNPsDSwHiXq4uRk0NCwETi\r
+       9NfrTBC2mMSFe+vZuhi5OIQE9jFKXF/3hhXC2cAo8WDLMyjnJJPEuX9roMqWMEpMOLeBBaSf\r
+       RUBV4uylmewgNpuAhsS2/csZQWwRASOJbc1bWUFsZgFpiW+/m8H2CQv4SBx5tIIZxOYV0JH4\r
+       t2M6kM0BNNRQ4thCHoiwoMTJmU9YIFq1JG78e8kEUgIyZvk/DhCTE2j6hFecIBWiAioSU05u\r
+       Y5vAKDQLSfMsJM2zEJoXMDKvYpRNya3SzU3MzClOTdYtTk7My0st0jXXy80s0UtNKd3ECA5q\r
+       F5UdjM2HlA4xCnAwKvHwHnieGCDEmlhWXJl7iFGSg0lJlPfFP6AQX1J+SmVGYnFGfFFpTmrx\r
+       IUYJDmYlEV5jkHLelMTKqtSifJiUNAeLkjjv9ZSb/kIC6YklqdmpqQWpRTBZGQ4OJQneA6xJ\r
+       AUKCRanpqRVpmTklCGkmDk6Q4TxAwwtAaniLCxJzizPTIfKnGBWlxHn7QRICIImM0jy4XljS\r
+       ecUoDvSKMO8mkCoeYMKC634FNJgJaDD/njiQwSWJCCmpBsbMN6YKph+m1Pm9OscxPWVLJbNJ\r
+       qv0z10Wz3yhxtG5nuX16mQZ3afc9sxgD4yL9q18d77c/98m/kuISo/3mWcr/zrVN7vecjU/2\r
+       9t7VbJ+2z+3/XctXCocNPjRGzA3pOMVuJqK7MM60VvdvaoPcA4OHS7aVfnaOf535aMO1CXfu\r
+       2C341bm866QSS3FGoqEWc1FxIgDUgfb2FQMAAA==\r
+Cc: notmuch@notmuchmail.org\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Tue, 25 Sep 2012 19:31:42 -0000\r
+\r
+Quoth Olivier Berger on Sep 25 at  6:03 pm:\r
+> Hi.\r
+> \r
+> Whenever a participant changes the subject in the middle of a thread,\r
+> the summary reported by notmuch search will change.\r
+> \r
+> However, the result is that some mails tend to "disappear" from search\r
+> results, when (bad) participants reply instead of composing a new mail,\r
+> and change a subject (see\r
+> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688699 for more details\r
+> on that problem, and a discussion). Of course, they're still there, but\r
+> their subject being masked, one may then grep or C-s for a particular\r
+> subject and miss them.\r
+> \r
+> I think it would be interesting to allow notmuch to potentially keep the\r
+> original subject and not the most recent one for the thread summaries.\r
+> \r
+> What do you think ?\r
+\r
+I think this would be fantastic.  I've proposed unconditionally\r
+showing the earliest subject before and it seems that people who\r
+correspond mostly with those who have good threading etiquette would\r
+prefer this change, but those who correspond with more people who use\r
+'reply' like an address book prefer the current behavior.\r
+\r
+Another option, which I'd like to experiment with but haven't found\r
+the time, is to show *all* distinct subjects for matched messages in a\r
+thread (modulo "Re:", etc) in the summary buffer, probably on multiple\r
+lines.  Since most threads only have a single unique subject, they\r
+would appear just as they do now, but it would be clear when someone\r
+(or something, like git) changed the subject mid-thread.  This\r
+approach would be far more robust while retaining good usability, but\r
+it would require more code than just changing our subject-picking\r
+heuristic.\r