Re: [PATCH] Drop deprecated/unused crypto.gpg_path

[Tomi Ollila]

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 struct were externally exposed, but it is not, so
> it's safe to unilaterally remove it.
>
> Signed-off-by: Daniel Kahn Gillmor 
> ---
>  bindings/python-cffi/tests/conftest.py | 2 --
>  doc/man1/notmuch-config.rst| 8 
>  notmuch-config.c   | 1 -
>  3 files changed, 11 deletions(-)

All code removal \o/ ! LGTM.

Tomi
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch

Re: [aperezdc/notmuch-addrlookup-c] Possibility to upstream (#23)

[David Bremner]

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 basically this:
>
> exec notmuch address from:"$*"
>
> I would love to be able to do `to:"$*"` here, but that gives the unexpected 
> result of the `From` addresses instead of `To` in that search... And 
> `--output=recipients` does not fix that at all...
>

If you have a way to reproduce this (e.g. that works with the notmuch
test corpus, or at least doesn't depend on your mail), please let us
know. I can't really understand the problem from the description here,
so it's not likely to get fixed.

PS this is not sent via github, as it's not about notmuch-addrlookup

___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch

[PATCH] Drop deprecated/unused crypto.gpg_path

[Daniel Kahn Gillmor]

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 
---
 bindings/python-cffi/tests/conftest.py | 2 --
 doc/man1/notmuch-config.rst| 8 
 notmuch-config.c   | 1 -
 3 files changed, 11 deletions(-)

diff --git a/bindings/python-cffi/tests/conftest.py 
b/bindings/python-cffi/tests/conftest.py
index e322cc64..de7db8e7 100644
--- a/bindings/python-cffi/tests/conftest.py
+++ b/bindings/python-cffi/tests/conftest.py
@@ -78,8 +78,6 @@ def maildir(tmppath):
 exclude_tags=deleted;spam;
 [maildir]
 synchronize_flags=true
-[crypto]
-gpg_path=gpg
 """.format(tmppath=tmppath)))
 return MailDir(tmppath)
 
diff --git a/doc/man1/notmuch-config.rst b/doc/man1/notmuch-config.rst
index 7347ad31..323a8b65 100644
--- a/doc/man1/notmuch-config.rst
+++ b/doc/man1/notmuch-config.rst
@@ -134,14 +134,6 @@ The available configuration items are described below.
 
 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``.
diff --git a/notmuch-config.c b/notmuch-config.c
index 1b079e85..19c2ddb3 100644
--- a/notmuch-config.c
+++ b/notmuch-config.c
@@ -119,7 +119,6 @@ struct _notmuch_config {
 bool is_new;
 
 char *database_path;
-char *crypto_gpg_path;
 char *user_name;
 char *user_primary_email;
 const char **user_other_email;
-- 
2.25.0

___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch