From: David Bremner <david@tethera.net>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>, notmuch@notmuchmail.org
Subject: Re: Binding access to ~/.notmuch-config
In-Reply-To: <5696343B.2070907@fastmail.net>
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>
 <5696343B.2070907@fastmail.net>
User-Agent: Notmuch/0.21+26~g9404723 (http://notmuchmail.org) Emacs/24.5.1
 (x86_64-pc-linux-gnu)
Date: Wed, 13 Jan 2016 08:25:10 -0400
Message-ID: <87wprd4qft.fsf@zancas.localnet>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list

Konrad Hinsen <konrad.hinsen@fastmail.net> writes:

> 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.

Yes, I understand that it's convenient, but the current set up is not
really very robust.  The python bindings are making assumptions about a
file format that has never been documented, and whose stability has
never been promised. It's roughly like calling private functions not
part of the published API. Sometimes it's the only way to do something,
but that doesn't mean it won't break. I think we'll eventually want to
provide some config related API, but having having arbitrary programs
reading and writing this file isn't it, IMHO.  In particular upcoming
changes may move some configuration items out of this file and into a
library level configuration API.

d