From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 08942431FBC for ; Thu, 2 Oct 2014 04:24:30 -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 PNONqYPlb6Pl for ; Thu, 2 Oct 2014 04:24:24 -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 AE90A431FB6 for ; Thu, 2 Oct 2014 04:24:24 -0700 (PDT) Received: from remotemail by yantan.tethera.net with local (Exim 4.80) (envelope-from ) id 1XZeUg-0000hg-UD; Thu, 02 Oct 2014 08:24:22 -0300 Received: (nullmailer pid 19523 invoked by uid 1000); Thu, 02 Oct 2014 11:24:18 -0000 From: David Bremner To: sshilovsky@gmail.com, notmuch@notmuchmail.org Subject: Re: notmuch-vim doesn't respect notmuch config defaults In-Reply-To: References: User-Agent: Notmuch/0.18.1+98~gae27403 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Thu, 02 Oct 2014 13:24:18 +0200 Message-ID: <87zjdeaf4t.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: Thu, 02 Oct 2014 11:24:30 -0000 Sergei Shilovsky writes: > I would suggest to use `notmuch config list` to get configuration > values in vim if possible I guess this is a general question we haven't really resolved, namely sharing configuration information between various notmuch frontends. .notmuch-config is really the configuration file for the notmuch CLI; it isn't read by library, so clients using language bindings won't see it at all by default. On a somewhat related note I've been thinking how to best associate configuration information with a database (see e.g. the thread at id:1411805835-3563-1-git-send-email-david@tethera.net ). Note that this would not help this particular case. Offhand, I wouldn't be personally to some interface at the library level wrapping the reading and writing of ~/.notmuch-config, although as I mentioned before, the size and complexity of notmuch-config.c perturb me a little as far as being suitable for library code. d