From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 906F06DE02A7 for ; Sat, 2 Apr 2016 05:41:21 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.021 X-Spam-Level: X-Spam-Status: No, score=-0.021 tagged_above=-999 required=5 tests=[AWL=-0.010, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8ainMvz3b9bJ for ; Sat, 2 Apr 2016 05:41:13 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id CEF6F6DE0281 for ; Sat, 2 Apr 2016 05:41:12 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.84) (envelope-from ) id 1amKs4-00023V-87; Sat, 02 Apr 2016 08:41:44 -0400 Received: (nullmailer pid 2988 invoked by uid 1000); Sat, 02 Apr 2016 12:41:08 -0000 From: David Bremner To: David Mazieres expires 2016-06-30 PDT , notmuch@notmuchmail.org Subject: Re: Breaking a really long thread In-Reply-To: <87twjkopb8.fsf@ta.scs.stanford.edu> References: <1459015043-8460-1-git-send-email-david@tethera.net> <87twjkopb8.fsf@ta.scs.stanford.edu> User-Agent: Notmuch/0.21+74~g6c60fb1 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Sat, 02 Apr 2016 09:41:08 -0300 Message-ID: <87a8lci3ob.fsf@zancas.localnet> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.20 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 Apr 2016 12:41:21 -0000 David Mazieres writes: > Is there any way to break an existing thread (so as to start over with a > smaller thread), or otherwise to tweak the threading rules so that a > particular References header gets ignored. Currently there is no way to do this, as threads are "stateless" i.e. created on the fly by _notmuch_create_thread based only on immutable mail data. We'd have to be willing to dump/restore any threading hints we added to the database, but we're already headed down that path with the libconfig stuff anyway. Something we _almost_ have the infrastructure in place for would be to blacklist a particular reference (e.g. by regex) by storing the blacklist as database metadata. That would solve your particular problem, although I'm not sure it it's general enough. Keeping global state for all thread breaking sounds a bit clunky. > It's annoyingly slow to open > a thread with 10,000 messages just to read one SMS. I'm almost tempted > to mangle the messages on delivery and remove the References header > before notmuch sees them, but it would be nice to have a cleaner > solution, as there are other situations in which one might want to > "reset" a really long thread. Like this thread ;).