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 4D7886DE0C1E for ; Wed, 3 Feb 2016 06:33:04 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.646 X-Spam-Level: X-Spam-Status: No, score=0.646 tagged_above=-999 required=5 tests=[AWL=-0.638, RCVD_IN_RP_RNBL=1.284] 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 Mq0-xyB3XvFM for ; Wed, 3 Feb 2016 06:32:57 -0800 (PST) Received: from ccx.webprojekty.cz (156.200.broadband11.iol.cz [90.178.200.156]) by arlo.cworth.org (Postfix) with ESMTP id AB8F46DE0B64 for ; Wed, 3 Feb 2016 06:32:57 -0800 (PST) Received: from dorje.v103.te2000 (unknown [82.142.125.46]) (Authenticated sender: ccx@webprojekty.cz) by ccx.webprojekty.cz (Postfix) with ESMTPSA id D80771176; Wed, 3 Feb 2016 14:38:19 +0100 (CET) Date: Wed, 3 Feb 2016 15:32:50 +0100 From: Jan Pobrislo To: David Bremner , notmuch@notmuchmail.org Subject: Re: [PATCH/RFC 0/3] Maildir custom flags and notmuch tags Message-ID: <20160203153250.56aa0b2b@dorje.v103.te2000> In-Reply-To: <87d1se9f2b.fsf@zancas.localnet> References: <1448504191-30974-1-git-send-email-igor.contato@gmail.com> <87mvsd7cxr.fsf@zancas.localnet> <20160202175220.12f8a712@dorje.v103.te2000> <87d1se9f2b.fsf@zancas.localnet> X-Mailer: Claws Mail 3.13.0 (GTK+ 2.24.28; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: Wed, 03 Feb 2016 14:33:04 -0000 On Wed, 03 Feb 2016 08:03:08 -0400 David Bremner wrote: > I see, you're talking about this "dovecot-keywords" file I guess > > http://wiki2.dovecot.org/MailboxFormat/Maildir Indeed. > Some questions that spring to mind: > > - This is clearly dovecot specific; I wonder what fraction of > our users would benefit. I suppose that's a question about any > scheme involving maildir-flags a-z; at least those can be > synchronized ootb by several tools. Every such maildir extension out there that I know of was invented for some specific application. Out of the two documented formats there are, the dovecot-keywords file is: 1) more limited (26 tags maximum) 2) simpler to implement, especially wrt. detecting changes 3) usable out of the box with some tools, as you noted Of course, one could go invent some another format, but in the end it'd be application-specific too, and I don't see it succeeding without help of mail-synchronizer authors. > - Notmuch new currently only indexes one copy of a message, so two > files in different maildirs (i.e. a list and inbox) would be pretty > much a crapshoot which tags get applied. We intend to change this > behaviour eventually, but no one is working on it currently. > > - even if/when this behaviour changes, there is still the problem of > reconciling different tag mappings from several maildirs. This is nothing new though, current synchronize_tags has the very same problem. I'm not sure how much of a problem it is in practice, but it probably should be addressed in some way. Here possibly the best course of action would be to leave it open-ended and provide user-definable conflict resolution hook, as I can't really think of "one size fits all" solution. > On the other hand, maybe not much change to the notmuch core would be > needed to at least experiment with this, using e.g. hooks to > notmuch-insert and notmuch-new. I was pondering this before and would find it rather neat, but it is bit more complicated than it might first seem. The hook needs to be able to add arbitrary files to be watched for changes and deduce from that which files need their tags re-read.