From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: bad epg.el+GPG2 behavior: unavoidable passphrase pinentry prompt
Date: Fri, 04 Oct 2013 17:05:25 -0400 [thread overview]
Message-ID: <87k3hssq5m.fsf@flea.lifelogs.com> (raw)
In-Reply-To: jwveh82tn9f.fsf-monnier+emacs@gnu.org
On Thu, 03 Oct 2013 10:59:13 -0400 Stefan Monnier <monnier@IRO.UMontreal.CA> wrote:
>> OK, so there's no way to avoid the broken behavior in epg.el and any
>> fixes on the GnuPG side have to wait until a new release (and someone,
>> possibly you, has to ask Werner for that fix). Is that accurate? It
SM> Can you make a bug report about the problematic behavior (e.g. with your
SM> previously posted recipe), and move the discussion there?
I don't think it's worthwhile after this discussion. I'll work around it
and see if I can make the workaround generally available.
Ted
next prev parent reply other threads:[~2013-10-04 21:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 9:22 bad epg.el+GPG2 behavior: unavoidable passphrase pinentry prompt Ted Zlatanov
2013-09-29 15:07 ` Thierry Volpiatto
2013-09-29 17:48 ` Ted Zlatanov
2013-09-29 15:24 ` Daiki Ueno
2013-09-29 17:57 ` Ted Zlatanov
2013-10-02 7:23 ` Daiki Ueno
2013-10-02 10:34 ` Ted Zlatanov
2013-10-02 12:48 ` Daiki Ueno
2013-10-02 13:27 ` Andrey Kotlarski
2013-10-02 13:38 ` Ted Zlatanov
2013-10-03 1:52 ` Daiki Ueno
2013-10-03 13:59 ` Ted Zlatanov
2013-10-03 14:59 ` Stefan Monnier
2013-10-04 21:05 ` Ted Zlatanov [this message]
2013-10-05 16:21 ` Stefan Monnier
2013-10-07 18:15 ` Ted Zlatanov
2013-10-07 22:46 ` Stefan Monnier
2013-10-04 0:12 ` Daiki Ueno
2013-10-04 16:11 ` Ted Zlatanov
2013-09-30 18:53 ` Stefan Monnier
2013-09-30 19:24 ` Ted Zlatanov
2013-09-30 22:49 ` Stefan Monnier
2013-09-30 23:34 ` Ted Zlatanov
2013-10-01 0:40 ` Stefan Monnier
2013-10-01 1:13 ` Ted Zlatanov
2013-10-01 2:23 ` Stephen J. Turnbull
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=87k3hssq5m.fsf@flea.lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@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).