Subject: Re: Binding access to ~/.notmuch-config
References: <5694CA65.8010400@fastmail.net> <87bn8r54dz.fsf@zancas.localnet>
 <m160yyev4o.fsf@fastmail.net> <8737u26cpg.fsf@zancas.localnet>
 <8760yy4o3w.fsf@tesseract.cs.unb.ca> <20160112191350.GE372@odin.tremily.us>
To: notmuch@notmuchmail.org
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
Message-ID: <5696343B.2070907@fastmail.net>
Date: Wed, 13 Jan 2016 12:25:47 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0)
 Gecko/20100101 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <20160112191350.GE372@odin.tremily.us>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: list

On 12/01/16 20:13, W. Trevor King wrote:

> On Tue, Jan 12, 2016 at 03:03:15PM -0400, David Bremner wrote:
>> Nothing to do with Konrad's crash, but I consider the fact that the
>> python bindings read ~/.notmuch-config to be a kind of layering
>> violation, since that file belongs to the CLI, while the bindings
>> are supposed to provide access to libnotmuch.
>
> I think of ~/.notmuch-config as being shared between all client code,
> and in that view it makes sense to have both the CLI and Python
> bindings (and other bindings) access it to figure out how to configure

I agree. I see notmuch as a collection of CLI tools, some of which are 
part of the distribution and others are written by myself for my 
specific needs. I'd like them all to share a single configuration file. 
In fact, I'd love to be able to add sections specific to my Python scripts.

Cheers,
   Konrad.