From: Damien Cassou <damien@cassou.me>
To: Gregor Zattler <telegraph@gmx.net>,
emacs-devel@gnu.org, Nicolas Petton <nicolas@petton.fr>
Subject: Re: [Emacs-diffs] master 29006a6: Detect if a message can be encrypted and add an MML tag
Date: Wed, 11 Apr 2018 13:44:13 +0200 [thread overview]
Message-ID: <87a7uax90y.fsf@cassou.me> (raw)
In-Reply-To: <87k1te567v.fsf@len.workgroup>
Gregor Zattler <telegraph@gmx.net> writes:
> run-hooks: Symbol’s function definition is void:
> message-add-encrypt-tag-if-can-encrypt when sending a email.
right. I will send a patch fixing the NEWS entry. Thanks for the report.
> 1) It adds the MML tags even if the recipients key is disabled.
I don't know what "the recipients key is disabled" means.
> 2) More complicated: The UI does not provide a means to
> temporarily not use encryption (when e.g. you know your
> correspondent is on vacation and reads email on a smartphone
> without decryption facilities). The only way to send an
> unencrypted email to a recipient for whom I have the
> corresponding pub key, is to delete
> message-sign-encrypt-if-all-keys-available from message-send-hook
> before sending.
I agree. We could add a boolean buffer-local variable that the user
could toggle with something like `M-x
message-toggle-sign-encrypt-if-all-keys-available`. This would only
affect the current buffer. What do you think?
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill
next prev parent reply other threads:[~2018-04-11 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180404183303.27542.7640@vcs0.savannah.gnu.org>
[not found] ` <20180404183305.17AB4202C3@vcs0.savannah.gnu.org>
2018-04-11 11:32 ` [Emacs-diffs] master 29006a6: Detect if a message can be encrypted and add an MML tag Gregor Zattler
2018-04-11 11:44 ` Damien Cassou [this message]
2018-04-11 13:07 ` Herring, Davis
2018-04-11 17:57 ` Gregor Zattler
[not found] <mailman.37408.1523451062.27992.emacs-devel@gnu.org>
2018-04-11 18:00 ` Jens Lechtenboerger
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=87a7uax90y.fsf@cassou.me \
--to=damien@cassou.me \
--cc=emacs-devel@gnu.org \
--cc=nicolas@petton.fr \
--cc=telegraph@gmx.net \
/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).