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 23913431FBF for ; Sat, 27 Sep 2014 23:27:47 -0700 (PDT) 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 6Ji6ckGWFaWZ for ; Sat, 27 Sep 2014 23:27:38 -0700 (PDT) Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id A4E97431FBD for ; Sat, 27 Sep 2014 23:27:38 -0700 (PDT) Received: from remotemail by yantan.tethera.net with local (Exim 4.80) (envelope-from ) id 1XY7xI-0001Z1-9k; Sun, 28 Sep 2014 03:27:36 -0300 Received: (nullmailer pid 29540 invoked by uid 1000); Sun, 28 Sep 2014 06:27:30 -0000 From: David Bremner To: Michal Sojka , notmuch@notmuchmail.org Subject: Re: [RFC] database: get and set mapping of dovecot compatible maildir keywords In-Reply-To: <87iok8vog6.fsf@steelpick.2x.cz> References: <1411805835-3563-1-git-send-email-david@tethera.net> <87iok8vog6.fsf@steelpick.2x.cz> User-Agent: Notmuch/0.18.1+98~gae27403 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Sun, 28 Sep 2014 08:27:30 +0200 Message-ID: <87bnq0feel.fsf@maritornes.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain 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: Sun, 28 Sep 2014 06:27:47 -0000 Michal Sojka writes: > I'd prefer having the mapping stored in the config file rather than in > the database. This would allow me to synchronize the configuration > between multiple computers. Would there be some benefit of having the > mapping (also) in the database? In retrospect, probably not that great a benefit, except I kindof dislike the idea of putting the mess that is notmuch-config.c into the library, so we'd likely have to deal with coming up with a clean config file mechanism. I agree that being able to sync plain text config probably trumps this.