unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: diego <dieggsy@protonmail.com>
To: "27445@debbugs.gnu.org" <27445@debbugs.gnu.org>
Subject: bug#27445: 26.0.50; Insufficient documentation for pinentry.el
Date: Mon, 27 Nov 2017 17:12:35 -0500	[thread overview]
Message-ID: <-DBV-SblJlEI5k3sa3TNoDit9oGkfcvxzv-MlBjckBPp7eQrkgJ0B1OpRopBp3iiTC3dUGnRQQVvZIi64QlbU_9f9zWMhpK-sJAvUiDfj7Q=@protonmail.com> (raw)
In-Reply-To: <87vano7ihu.fsf@drachen>

I see pinentry.el was removed from emacs master - is it worth mentioning it did more than the functionality stated as making it obsolete?

For example, as long as INSIDE_EMACS was set, I could decrypt files using gpg from eshell or term and be prompted through the minibuffer, and git could sign commits while prompting through the minibuffer as well. 

I guess I'm saying it seems to me that pinentry.el had more use than just being used by epa. 

​- diego

​







  parent reply	other threads:[~2017-11-27 22:12 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
2017-11-27 22:12 ` diego [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='-DBV-SblJlEI5k3sa3TNoDit9oGkfcvxzv-MlBjckBPp7eQrkgJ0B1OpRopBp3iiTC3dUGnRQQVvZIi64QlbU_9f9zWMhpK-sJAvUiDfj7Q=@protonmail.com' \
    --to=dieggsy@protonmail.com \
    --cc=27445@debbugs.gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).