unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: ueno@gnu.org
Cc: michael_heerdegen@web.de, 27445@debbugs.gnu.org
Subject: bug#27445: 26.0.50; Insufficient documentation for pinentry.el
Date: Sat, 18 Nov 2017 11:50:45 +0200	[thread overview]
Message-ID: <83zi7jgbka.fsf@gnu.org> (raw)
In-Reply-To: <83vaiz63f3.fsf@gnu.org> (message from Eli Zaretskii on Sat, 28 Oct 2017 12:13:20 +0300)

Ping!

> Date: Sat, 28 Oct 2017 12:13:20 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 27445@debbugs.gnu.org
> 
> > From: Michael Heerdegen <michael_heerdegen@web.de>
> > Date: Thu, 26 Oct 2017 14:00:27 +0200
> > 
> > Michael Heerdegen <michael_heerdegen@web.de> writes:
> > 
> > > I'm thankful that I had the luck to be able to restore the previous
> > > state so that I got my Email working again and could open this report.
> > > This should not happen to others.
> > 
> > I discovered by accident that
> > 
> > #+begin_src emacs-lisp
> >   (setq epa-pinentry-mode 'loopback)
> > #+end_src
> > 
> > does what I want.
> > 
> > It would still be good to have some page in the manual that describes
> > with what tools file encryption in Emacs is done, and where to look for
> > documentation.  Currently there is only a description of encryption
> > commands of dired (info "(emacs) Operating on Files").
> 
> I agree.
> 
> Daiki, could you please add some user-level documentation about this
> package?





  reply	other threads:[~2017-11-18  9:50 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 [this message]
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
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=83zi7jgbka.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=27445@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    --cc=ueno@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).