From: Ted Zlatanov <tzz@lifelogs.com>
To: Daiki Ueno <ueno@gnu.org>
Cc: 24553@debbugs.gnu.org, Nick Helm <nick@tenpoint.co.nz>
Subject: bug#24553: 25.1; epa ignores epg-gpg-program in very confusing way
Date: Mon, 03 Oct 2016 13:41:19 -0400 [thread overview]
Message-ID: <8760p9wcsg.fsf@lifelogs.com> (raw)
In-Reply-To: <od1twcy66u2.fsf-ueno@gnu.org> (Daiki Ueno's message of "Thu, 29 Sep 2016 17:53:09 +0200")
On Thu, 29 Sep 2016 17:53:09 +0200 Daiki Ueno <ueno@gnu.org> wrote:
DU> Nick Helm <nick@tenpoint.co.nz> writes:
>>> I need to edit some files that decrypt properly with gpg 1.4 but not gpg
>>> 2.1. I have both installed on my system, with 1.4 as /usr/bin/gpg1 and
>>> 2.1 as /usr/bin/gpg2. The bug is that emacs ignores the epg-gpg-program
>>> variable *except* in error messages, which is very confusing.
>>
>>> Ideally emacs should obey epg-gpg-program ...
>>
>> I have a similar problem with epg-gpg-program. See bug#24229
>> (https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24229) for some
>> discussion that might be relevant.
DU> And I want to close this as a duplicate of that bug. Is there still
DU> anything we can technically do for this? Isn't it enough to suggest:
DU> M-: (custom-set-variables '(epg-gpg-program "gpg1" t))
DU> instead of setq?
Respectfully, the usability bug here is different: EPA/EPG only uses the
customized value, while the log message only uses the actual value in
the variable. So the log messages should be adjusted, if you want to
keep using the customized value only in EPA/EPG. And perhaps they should
catch and mention the case where the customized value is not the same as
the variable value, again for usability's sake.
HTH
Ted
next prev parent reply other threads:[~2016-10-03 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 8:15 bug#24553: 25.1; epa ignores epg-gpg-program in very confusing way 16emacsbug
2016-09-29 3:07 ` Nick Helm
2016-09-29 15:53 ` Daiki Ueno
2016-10-03 17:41 ` Ted Zlatanov [this message]
2017-03-10 20:16 ` Glenn Morris
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=8760p9wcsg.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=24553@debbugs.gnu.org \
--cc=nick@tenpoint.co.nz \
--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).