Date: Tue, 12 Jan 2016 11:13:50 -0800
From: "W. Trevor King" <wking@tremily.us>
To: David Bremner <david@tethera.net>
Cc: notmuch@notmuchmail.org
Subject: Binding access to ~/.notmuch-config (was: Crash with Python bindings)
Message-ID: <20160112191350.GE372@odin.tremily.us>
References: <5694CA65.8010400@fastmail.net> <87bn8r54dz.fsf@zancas.localnet>
 <m160yyev4o.fsf@fastmail.net> <8737u26cpg.fsf@zancas.localnet>
 <8760yy4o3w.fsf@tesseract.cs.unb.ca>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature"; boundary="2LWaEC9akcLlisSC"
Content-Disposition: inline
In-Reply-To: <8760yy4o3w.fsf@tesseract.cs.unb.ca>
OpenPGP: id=39A2F3FA2AB17E5D8764F388FC29BDCDF15F5BE8;
 url=http://tremily.us/pubkey.txt
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: list


--2LWaEC9akcLlisSC
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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
their library access calls.  Having a separate config file for each
client to point at the default database path seems like more trouble
than it's worth, as does adding a library function for =E2=80=9Creach into
some local config and return the default database path=E2=80=9D.

Cheers,
Trevor

--=20
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

--2LWaEC9akcLlisSC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJWlVBtAAoJEAPqygegUbGsyYoP/0Bak9MknN/I6ZeusBKuwFmF
d92q2aGtEuWyXETfhhtgoweGIj5w5FGJwgMFTEWkoFcft3ORRHI4DiM7nJAsbfQx
g8f0Tqjr2UBN8qijZ1KemPdDY16tG7+4BASAkfSQFRlEUTPcea5+hMAU1q1RLOji
9vnuyBzkvWdjAbx+3FGGEdfc2equ/o5PyA5WDZtvOHCQfWoItRwbYPfeh7Xd206Q
JZosZqX/LwAMcNRXR3I1m2sYrYQ+Mz5f3H30koy32Ar2NEoagMJYMW5FRRn2DrCF
IdS7UTgxjjnEiTgvb86E1ojq8xguGwsPXzkQow1aTlBmI2JB+ZYVlxTv/+W8DnWB
Nbt4hQwRPG4dfvJ6W3h9UJDTWSa7+t07fUG0U/q0cNZ4vqVEc2t8iwXLPI/s9RrE
re1iba1N3Fy/yNc9K4rLWvSLq9dbZA0dO2nfqu8+xj+jQrkpCGIGAYDM9cf/eop1
4FG9gsfK7AxKqRBRisTPcwVSsF/GK77nv4c6mx3CTflmm4Y47F/O2lJjFx9yn81k
Iey2EYqKpFgC660UDju0+YuYoErU0vgkfSyqBfZF3SIqi10VWPZeaMZ2BV1NEkw+
OqTnPiCkUuYU8CQDvmn0dFacNGSrAyJm2VbH32iFyIUX5i9f/ZU2/FeLdWHKooi8
Eb5JWae1eB0VHXJX3Zlb
=awB4
-----END PGP SIGNATURE-----

--2LWaEC9akcLlisSC--