crypto.gpg_path was only used when we built against gmime versions
before 3.0. Since we now depend on gmime 3.0.3 or later, it is
meaningless.
The removal of the field from the _notmuch_config struct would be an
ABI change if that struct were externally exposed, but it is not, so
it's safe to
anarcat writes:
> One improvement we could *already* do with notmuch-address would be to
> enforce searching for to/from headers, which doesn't seem to be the case
> right now. I have a [wrapper
> script](https://gitlab.com/anarcat/scripts/-/blob/master/notmuch-address)
> where I do
On Tue, Feb 18 2020, Daniel Kahn Gillmor wrote:
> crypto.gpg_path was only used when we built against gmime versions
> before 3.0. Since we now depend on gmime 3.0.3 or later, it is
> meaningless.
>
> The removal of the field from the _notmuch_config struct would be an
> ABI change if that
