unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: , 46138@debbugs.gnu.org, Alexey Shmalko <rasen.dubi@gmail.com>
Subject: bug#46138: 28.0.50; epg--filter-revoked-keys filters out valid keys
Date: Sun, 31 Jan 2021 08:49:05 +0000	[thread overview]
Message-ID: <87h7mxmqym.fsf@yandex.com> (raw)
In-Reply-To: <87a6spv9yz.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 31 Jan 2021 08:31:16 +0100")

>>>>> Lars Ingebrigtsen <larsi@gnus.org> writes:

    > Colin Baxter <m43cap@yandex.com> writes:
    >> Forgive me for butting in. Should not the email address be
    >> escaped as rasen.dubi@gmail\.com? If you use
    >> 'epa-file-encrypt-to' as a 'add-file-local-variable-prop-line'
    >> then the escape is automatically inserted when entering an email
    >> address value.

    > I'm unable to reproduce that (which would be kinda odd, since the
    > variable is a string, not a regexp?)

    > If I load a file /tmp/test.gpg with:

    > ;; -*- epa-file-encrypt-to: ("test@gnus.org") -*-

    > (defun test ())

    > then the variable is ("test@gnus.org").

What you write is correct and -*- epa-file-encrypt-to:
("name@email.org") -*- is what I always used. However, I was curious
about using M-x add-file-local-variable-prop-line. Entering
epa-file-encrypt-to <RET> asks for "value" but without specifying string
or regexp. I stupidly just entered the email address without quotes. I
now know better. Perhaps the user should be given more information when
epa-file-encrypt-to asks for the value?

Thanks for correcting my mistake.

Best wishes,

Colin Baxter.





  reply	other threads:[~2021-01-31  8:49 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 [this message]
2021-01-31 10:15             ` Colin Baxter
2021-02-02  9:38       ` Alexey Shmalko
2021-02-02 12:01         ` Colin Baxter
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=87h7mxmqym.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).