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 unilaterally remove it.
Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
exclude_tags=deleted;spam;
[maildir]
synchronize_flags=true
- [crypto]
- gpg_path=gpg
""".format(tmppath=tmppath)))
return MailDir(tmppath)
Default: ``true``.
-**crypto.gpg_path**
- Name (or full path) of gpg binary to use in verification and
- decryption of PGP/MIME messages. NOTE: This configuration item is
- deprecated, and will be ignored if notmuch is built against GMime
- 3.0 or later.
-
- Default: ``gpg``.
-
**index.decrypt** **[STORED IN DATABASE]**
Policy for decrypting encrypted messages during indexing. Must be
one of: ``false``, ``auto``, ``nostash``, or ``true``.
bool is_new;
char *database_path;
- char *crypto_gpg_path;
char *user_name;
char *user_primary_email;
const char **user_other_email;