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 52489431FB6 for ; Wed, 6 Feb 2013 10:39:36 -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 7XDWHLgwVlkD for ; Wed, 6 Feb 2013 10:39:35 -0800 (PST) X-Greylist: delayed 1184 seconds by postgrey-1.32 at olra; Wed, 06 Feb 2013 10:39:35 PST Received: from imarko.xen.prgmr.com (imarko.xen.prgmr.com [72.13.95.244]) by olra.theworths.org (Postfix) with ESMTP id 9F832431FAF for ; Wed, 6 Feb 2013 10:39:35 -0800 (PST) Received: from localhost ([127.0.0.1] helo=zsu.kismala.com) by imarko.xen.prgmr.com with esmtp (Exim 4.80.1) (envelope-from ) id 1U39b4-0004Sa-G3 for notmuch@notmuchmail.org; Wed, 06 Feb 2013 10:19:50 -0800 From: Istvan Marko To: notmuch@notmuchmail.org Subject: Re: Reply all - issue References: <000001cdfcd9$82500f00$86f02d00$@nl> <000001ce0161$5da40990$18ec1cb0$@nl> Date: Wed, 06 Feb 2013 10:19:50 -0800 In-Reply-To: (=?utf-8?Q?=22Micha=C5=82?= Nazarewicz"'s message of "Mon, 4 Feb 2013 11:39:44 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.91 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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: Wed, 06 Feb 2013 18:39:36 -0000 Micha=C5=82 Nazarewicz writes: > I was actually wondering that instead of hard coding the logic into notmu= ch > itself, maybe it would be better to provide some sort of "split-thread" a= nd > "join-threads" which could than be used by separate tagging tool. Such a customized threading feature would be great, I would use it to tie together "loose threads" originating from crappy ticket tracking tools that don't insert any In-Reply-To or References headers. Currently I handle this by inserting fake In-Reply-To headers during delivery and I would love to have a cleaner way. To make this useful it would have to be persistent across dumps and restores.=20 If we only consider splitting then a relatively easy way might be to allow the user to configure some tags to mark a split. In .notmuch-config you'd have: split_tags: split And then you'd tag +split the message to mark the start of a new thread. The threading code would watch for such tags. Which might get hairy if the tag information is not already at hand during threading. I don't see how this would work for joins so it would not help me but it could address the original problem. --=20 Istvan