From: Daiki Ueno <ueno@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 27445@debbugs.gnu.org
Subject: bug#27445: 26.0.50; Insufficient documentation for pinentry.el
Date: Tue, 21 Nov 2017 07:19:06 +0100 [thread overview]
Message-ID: <87y3n08885.fsf-ueno@gnu.org> (raw)
In-Reply-To: <877eukvj7v.fsf@web.de> (Michael Heerdegen's message of "Mon, 20 Nov 2017 20:33:08 +0100")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> I don't fully understand the backgrounds. Does what you say mean that
> the problem will go away very soon (even on Debian) from alone?
As I said in the previous post:
> Fortunately, GnuPG 2.0 will be unsupported in the next month. After
> that we should be able to obsolete or remove the package.
As long as we support only GnuPG >= 2.1 and GnuPG 1.x, there is a way to
intercept passphrase prompt. In that case, there will be no need to use
a kludge like pinentry.el (+ emacs support in GnuPG/pinentry).
Regards,
--
Daiki Ueno
next prev parent reply other threads:[~2017-11-21 6:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 4:29 bug#27445: 26.0.50; Insufficient documentation for pinentry.el Michael Heerdegen
2017-10-26 12:00 ` Michael Heerdegen
2017-10-28 9:13 ` Eli Zaretskii
2017-11-18 9:50 ` Eli Zaretskii
2017-11-19 7:07 ` Daiki Ueno
2017-11-20 17:55 ` Andy Moreton
2017-11-21 12:15 ` Daiki Ueno
2017-11-21 15:56 ` Eli Zaretskii
2017-11-21 19:59 ` Daiki Ueno
2017-11-22 15:46 ` Eli Zaretskii
2017-11-22 16:18 ` Daiki Ueno
2017-11-23 1:06 ` Michael Heerdegen
2017-11-23 5:08 ` Daiki Ueno
2017-11-24 7:04 ` Michael Heerdegen
2017-11-24 10:49 ` Daiki Ueno
2017-11-24 13:40 ` Eli Zaretskii
2017-11-24 15:04 ` Daiki Ueno
2017-11-24 15:41 ` Eli Zaretskii
2017-11-24 17:54 ` Richard Stallman
2017-11-20 19:33 ` Michael Heerdegen
2017-11-21 6:19 ` Daiki Ueno [this message]
2017-11-27 22:12 ` diego
2017-12-12 9:19 ` Rasmus
2017-12-22 9:49 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3n08885.fsf-ueno@gnu.org \
--to=ueno@gnu.org \
--cc=27445@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.