From: Michael Piotrowski <mxp@dynalabs.de>
To: ding@gnus.org
Subject: Re: Encryption asking for recipients
Date: Tue, 01 Mar 2011 01:33:53 +0100 [thread overview]
Message-ID: <x6vd03wufi.fsf@eurus.zrh.dynalabs.de> (raw)
In-Reply-To: <m3wrkk6gph.fsf-ueno@unixuser.org>
On 2011-02-28, Daiki Ueno <ueno@unixuser.org> wrote:
>> I'm not sure when it started, but it's also in the latest git pull:
>> When encrypting a message, `mml2015-epg-encrypt' is apparently unable
>> to get the recipient from the message and prompts for them.
[...]
> Could you try to edebug `mml2015-epg-encrypt'?
I've found the problem: It's not `mml2015-epg-encrypt' but rather a
change in message.el.
Commit d7f2cb176d4c7dfad075e3914bdde41553ef5a9f makes message-options a
buffer-local variable. This change essentially breaks encryption on
XEmacs 21.4.22. I'm all for clean code, but I'd suggest to either
revert this change or make it conditional.
Greetings
--
Dr.-Ing. Michael Piotrowski, M.A. <mxp@dynalabs.de>
Public key at <http://www.dynalabs.de/mxp/pubkey.txt> (ID 0x1614A044)
prev parent reply other threads:[~2011-03-01 0:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 23:51 Michael Piotrowski
2011-02-28 2:22 ` Daiki Ueno
2011-02-28 12:48 ` Michael Piotrowski
2011-03-01 0:33 ` Michael Piotrowski [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x6vd03wufi.fsf@eurus.zrh.dynalabs.de \
--to=mxp@dynalabs.de \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).