> It looks nice. A little bit more cheerful than I would have chosen by
> default, but maybe that's good ;).

Thanks!

> In the docs, you write
> 
>   If your notmuch configuration is a non-standard place, you can specify
>   this by setting the NOTMUCH_CONFIG environment variable. Note that the
>   Python API only picks up options that are included in the
>   database. You may have to run e.g.
> 
>         notmuch config set --database search.exclude_tags 'deleted'
> 
> This sounds a bit odd to me; modern notmuch should transparently merge
> config information from the text config file and the database. I suspect
> this might be related to my next question.
> 
> It looks like you are using the legacy bindings. I was literally
> planning on removing those from the next upstream release, so I hope
> either I'm wrong or you can migrate easily to the cffi bindings (called
> notmuch2 most places).

Ah, yes, the two separate APIs caused some confusion. It wasn't clear to me that 
one was going to go away and one essentially deprecated, so I went with the 
legacy bindings because they seemed to be better supported in my system's 
packages.

I'll update that; shouldn't be too much work. And if that solves the 
configuration issues that's even better!

Cheers,

Lars
_______________________________________________
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-leave@notmuchmail.org