On Thu, 14 Nov 2019 19:54, Ralph Seichter said:
> $ cat /tmp/pinentry-wrapper.log
> INSIDE_EMACS is ''
Pinentry consideres that it is not run from Emacs and thus it does not
forward requests to Emacs but uses the standard pinentry (or should
return an error for pinentry-emacs). INSIDE_EMACS
* Filipp Gunbin via Gnupg-users:
> I see this in NEWS for Emacs 27.1 (unreleased master).
>
> --8<---cut here---start->8---
> *** 'epa-pinentry-mode' is renamed to 'epg-pinentry-mode'.
> It now applies to epg functions as well as epa functions.
I tried both epa
* Werner Koch via Gnupg-users:
> ${TMPDIR-/tmp}/emacs$(id -u)/pinentry
The socket exists and the permissions look OK (read/write access for my
Linux user).
> If you insert a pinentry wrapper, can you see the INSIDE_EMACS envvar?
I just tried the following wrapper script:
#!/usr/bin/env bash
On 13/11/2019 17:58 +0100, Ralph Seichter wrote:
> * Filipp Gunbin via Gnupg-users:
>
>> I have 2.2.17 and it works with empty gpg-agent.conf and just this
>> line in .emacs:
>> (setq epg-pinentry-mode 'loopback)
>
> I use the same GnuPG version, but the Emacs variable setting you
> suggested make
Sorry, previous message went unfinished.
On 13/11/2019 17:58 +0100, Ralph Seichter wrote:
> I use the same GnuPG version, but the Emacs variable setting you
> suggested makes no difference for me. That's Emacs version 26.3,
> which I should have mentioned earlier.
I see this in NEWS for Emacs 27
On Wed, 13 Nov 2019 17:58, Ralph Seichter said:
> I use the same GnuPG version, but the Emacs variable setting you
> suggested makes no difference for me. That's Emacs version 26.3,
> which I should have mentioned earlier.
Yet another regression in Emacs? I am still cursing over 26.
Fortunately
