This reverts commit 12f7d4e61d30fb9a5c99e128ab1aab0bf069cdb4.
Since we're not using gpgconf anymore, drop the unneeded test in
configure.
---
configure | 16
1 file changed, 16 deletions(-)
diff --git a/configure b/configure
index 46063b5d..f1773044 100755
--- a/configure
+++ b/
We already use this directory for dtach sockets, so it makes sense to
put gnupg sockets there as well. There doesn't seem to be a clean way
to put a fully functional socket in a different location than
GNUPGHOME.
---
test/test-lib-common.sh | 1 -
test/test-lib.sh| 2 ++
2 files changed, 2
It turns out the hardcoded use of /run/user in gpg doesn't work out
that well in some environments, particularly autobuilders, since
creating those directories is typically done by some login session
manager like systemd-logind (or pam_systemd to be more precise).
This is a more low-tech attempt,
This reverts commit e7b88e8b0a93ca83d807edc00e0c97af54c5b5f1.
It turns out that this does not work well in environments without a
running systemd (or some other provider of /run/user)
---
test/test-lib.sh | 14 --
1 file changed, 14 deletions(-)
diff --git a/test/test-lib.sh b/test/t
Mark Walters writes:
> Hi
>
>>> But what will we do if the user has not customized it because she
>>> /wants/ to display all possible things inline. I have not seen that this
>>> patch is merged into master, and probably, when I have learned about
>>> this variable, I think maybe it's better not
On Sun, Feb 26 2017, Jani Nikula wrote:
> The help command does not really need to try to open the config
> file. So don't.
>
> ---
This series looks good, tests pass, repost of my patch seems to be
unmodified (the power of running 2 emacses w/ notmuch rules!)
In addition to `make test` I ran t
Where to obtain notmuch 0.23.6
===
https://notmuchmail.org/releases/notmuch-0.23.6.tar.gz
Which can be verified with:
https://notmuchmail.org/releases/notmuch-0.23.6.tar.gz.sha1
0be0f43f46898fdc00f460b1e50df0be6700fdfc notmuch-0.23.6.tar.gz
https://notmuchmail.o
On Mon, Feb 27 2017, Mark Walters wrote:
> Hi
>
>>> But what will we do if the user has not customized it because she
>>> /wants/ to display all possible things inline. I have not seen that this
>>> patch is merged into master, and probably, when I have learned about
>>> this variable, I think ma
Hi
>> But what will we do if the user has not customized it because she
>> /wants/ to display all possible things inline. I have not seen that this
>> patch is merged into master, and probably, when I have learned about
>> this variable, I think maybe it's better not to do it in the notmuch
>> co
