unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jens Lechtenboerger <jens.lechtenboerger@fsfe.org>
Cc: 26090@debbugs.gnu.org
Subject: bug#26090: 26.0.50; Documentation for epg-gpg-program not sufficient
Date: Fri, 26 Jul 2019 13:57:37 +0200	[thread overview]
Message-ID: <87k1c5m2j2.fsf@mouse.gnus.org> (raw)
In-Reply-To: <87mvcpgf0c.fsf@informationelle-selbstbestimmung-im-internet.de> (Jens Lechtenboerger's message of "Mon, 13 Mar 2017 20:20:35 +0100")

Jens Lechtenboerger <jens.lechtenboerger@fsfe.org> writes:

> I fail to see that this is a reasonable behavior (why initialize that
> variable to gpg2 in the first place although that value will be
> ignored?), but at least it needs to be documented.

That is indeed curious behaviour, but perhaps there's historical reasons
for this...

> +Note that if this variable has the default value \"gpg2\" and
> +if your version of gpg is 2.0.x (instead of the modern variant
> +2.1.x), then gpg 1.x will be used (if it is installed) regardless
> +of this variable.  If you really want to use gpg2 version 2.0.x,
> +you need to \\[customize] this variable to \"gpg2\" (even if that
> +is its default value)."

I think this is essentially correct (I've read the code now, and this is
indeed what seems to be happening).  But I think I'll rephrase it a bit
and say something about how this variable is just a mild preference
unless actually customized.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2019-07-26 11:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-13 19:20 bug#26090: 26.0.50; Documentation for epg-gpg-program not sufficient Jens Lechtenboerger
2019-07-26 11:57 ` Lars Ingebrigtsen [this message]

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=87k1c5m2j2.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=26090@debbugs.gnu.org \
    --cc=jens.lechtenboerger@fsfe.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).