unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: Alexey Shmalko <rasen.dubi@gmail.com>
Cc: , Lars Ingebrigtsen <larsi@gnus.org>, 46138@debbugs.gnu.org
Subject: bug#46138: 28.0.50; epg--filter-revoked-keys filters out valid keys
Date: Tue, 02 Feb 2021 12:01:09 +0000	[thread overview]
Message-ID: <87y2g6y8ze.fsf@yandex.com> (raw)
In-Reply-To: <87czxidd1y.fsf@gmail.com> (Alexey Shmalko's message of "Tue, 02 Feb 2021 11:38:49 +0200")

>>>>> Alexey Shmalko <rasen.dubi@gmail.com> writes:

    > Use setq-local: C-x C-f /tmp/new-file.gpg RET foo M-: (setq-local
    > epa-file-encrypt-to "rasen.dubi@gmail.com") RET C-x C-s

    > or file local variables: # -*- epa-file-encrypt-to:
    > ("DCEF7BCCEB3066C3"); -*-

After having set the 'epa-file-encrypt-to' variable, by whatever means,
why does a list of possible keys then appear when the encrypted file is
saved? I would have thought that to be unnecessary since the key has
supposedly been already chosen via the 'epa-file-encrypt-to' variable. If
not then why set 'epa-file-encrypt-to'?

Best wishes,

Colin Baxter.





  reply	other threads:[~2021-02-02 12:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27 17:35 bug#46138: 28.0.50; epg--filter-revoked-keys filters out valid keys Alexey Shmalko
2021-01-28  5:17 ` Lars Ingebrigtsen
2021-01-29 15:35   ` Alexey Shmalko
2021-01-30  6:45     ` Lars Ingebrigtsen
2021-01-30 14:46       ` Colin Baxter
2021-01-31  7:31         ` Lars Ingebrigtsen
2021-01-31  8:49           ` Colin Baxter
2021-01-31 10:15             ` Colin Baxter
2021-02-02  9:38       ` Alexey Shmalko
2021-02-02 12:01         ` Colin Baxter [this message]
2021-02-02 12:16           ` Colin Baxter
2021-02-03 20:23           ` Alexey Shmalko
2021-02-04  7:25             ` Colin Baxter
2021-02-04  8:25         ` Lars Ingebrigtsen

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=87y2g6y8ze.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=46138@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=rasen.dubi@gmail.com \
    /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).