From: Lars Ingebrigtsen <larsi@gnus.org>
To: Teemu Likonen <tlikonen@iki.fi>
Cc: 25155@debbugs.gnu.org
Subject: bug#25155: 25.1.90; Gnus: Sending a GnuPG-signed message executes the signing operation twice when using gcc field in the message (annoyance with smartcards)
Date: Mon, 23 Sep 2019 02:16:37 +0200 [thread overview]
Message-ID: <878sqfeuje.fsf@gnus.org> (raw)
In-Reply-To: <871sxgw4aj.fsf@iki.fi> (Teemu Likonen's message of "Sat, 10 Dec 2016 10:56:36 +0200")
Teemu Likonen <tlikonen@iki.fi> writes:
> Would a single sign operation suffice in Gnus? After all, it's just two
> copies of the same message?
Indeed. But, man, was this difficult to debug, because putting a
`debug' statement into any of the mml functions just didn't work. It
turns out you had to say
(let ((inhibit-redisplay nil))
(debug))
to get it to debug. (I've now amended the doc string.)
So that took like nine hours, and it turns out that (logically enough)
the second call to the encoding function is done from
`gnus-inews-do-gcc'. It doesn't really know anything about what may
have happened before -- it just interprets the Gcc header, and then
calls `message-encode-message-body', which will encode the data again.
So to avoid the double encoding, Message needs some way to tell this
function not do to that, but instead cache the encoded value and make
`gnus-inews-do-gcc' use that instead. Hm... Perhaps a buffer-local
variable will do the trick...
I think I'll have a look at that tomorrow.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-09-23 0:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 8:56 bug#25155: 25.1.90; Gnus: Sending a GnuPG-signed message executes the signing operation twice when using gcc field in the message (annoyance with smartcards) Teemu Likonen
2019-09-23 0:16 ` Lars Ingebrigtsen [this message]
2019-09-23 9:46 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878sqfeuje.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=25155@debbugs.gnu.org \
--cc=tlikonen@iki.fi \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.