[notmuch] hijacked threads can be confusing in notmuch

diff --git a/f3/fd5ae0f312551538b6e1fdca82043471fa3061 b/f3/fd5ae0f312551538b6e1fdca82043471fa3061
new file mode 100644 (file)
index 0000000..b82d5cb
--- /dev/null
+++ b/f3/fd5ae0f312551538b6e1fdca82043471fa3061
@@ -0,0 +1,89 @@
+Return-Path: <bart@jukie.net>\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 E88D1431FBC\r
+       for <notmuch@notmuchmail.org>; Sat, 21 Nov 2009 18:18:35 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\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 ABqfQiGNTmtd for <notmuch@notmuchmail.org>;\r
+       Sat, 21 Nov 2009 18:18:35 -0800 (PST)\r
+Received: from tau.jukie.net (tau.jukie.net [216.239.93.128])\r
+       by olra.theworths.org (Postfix) with ESMTP id 0BB1E431FAE\r
+       for <notmuch@notmuchmail.org>; Sat, 21 Nov 2009 18:18:35 -0800 (PST)\r
+Received: by tau.jukie.net (Postfix, from userid 1000)\r
+       id 5AD98C05601; Sat, 21 Nov 2009 21:18:34 -0500 (EST)\r
+Date: Sat, 21 Nov 2009 21:18:34 -0500\r
+From: Bart Trojanowski <bart@jukie.net>\r
+To: notmuch@notmuchmail.org\r
+Message-ID: <20091122021833.GC17268@jukie.net>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=iso-8859-1\r
+Content-Disposition: inline\r
+Content-Transfer-Encoding: quoted-printable\r
+User-Agent: Mutt/1.5.18 (2008-05-17)\r
+Subject: [notmuch] hijacked threads can be confusing in notmuch\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.12\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: Sun, 22 Nov 2009 02:18:36 -0000\r
+\r
+I'd like to see how other people feel about a problem I just ran into.\r
+\r
+I wanted to look at the 'notmuch count' patch that Keith Packard posted\r
+a couple of days ago (as I am porting his folder mode to notmuch.vim).\r
+\r
+I was unable to find it using notmuch because he happened to post 3\r
+patches in one go.  It's pretty common git practice, and by no means to\r
+I hold Keith responsible :)\r
+\r
+In mutt it looked like this:\r
+\r
+  [notmuch] [PATCH 1/3] Make mouse-1 click in search view show thread\r
+  =E2=94=94=E2=94=80>[notmuch] [PATCH 2/3] Add 'notmuch count' command to s=\r
+how the count of matching messages\r
+    =E2=94=94=E2=94=80>[notmuch] [PATCH 3/3] Add notmuch-index mode to disp=\r
+lay message counts\r
+\r
+=2E.. and in the mutt threaded display the relationship between the three\r
+messages is pretty clear.\r
+\r
+Now consider what happens when I run notmuch search 'notmuch count'.  I\r
+get this:\r
+\r
+  Today 02:15 [2/3] Keith Packard; [notmuch] [PATCH 1/3] Make mouse-1 click=\r
+ in search view show thread (inbox unread)\r
+\r
+This thread happens to look completely unrelated to my search at first\r
+glance.  So naturally, I dismissed it.  I finally clued in what was\r
+happening and came back to it after.\r
+\r
+On a related note, one mail related pet peeve I have is when people\r
+reply to a random email in their mailbox when they actually intend to\r
+start a new thread.  Doing that would totally mess up someone using\r
+notmuch.  They could get search results with threads which have no\r
+relevance to their actual search... at least at first glance.\r
+\r
+So is there something better that we could do when detecting hijacked\r
+threads like this?  Is it safe to cut threads when you notice a topic\r
+change?  Or maybe it would be better to just mark such threads in the\r
+output of notmuch-search (either a boolean flag, or a count of topic\r
+changes).\r
+\r
+Anyone know how Gmail deals with this?\r
+\r
+Cheers,\r
+-Bart\r
+\r
+--=20\r
+                               WebSig: http://www.jukie.net/~bart/sig/\r