From: Hans de Graaff <hans@degraaff.org>
Subject: Problem with new sign+encrypt code
Date: Sun, 12 May 2002 16:39:18 +0200 [thread overview]
Message-ID: <877km9ig6h.fsf@graaff.xs4all.nl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 513 bytes --]
Hi,
After updating to the latest CVS version this morning I encountered
problems sending signed mail. I got messages like:
Warning, attempt to set invalid signencrypt-style
in the minibuffer. I traced this back to the mml-generate-mime-1
function in mml.el. There mml-signencrypt-style was called with a null
argument, because my buffer only contained a sign component, and not
an encrypt component. The following patch seems to fix that, but I'm
not sure if this is the proper fix.
Hans
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: mml.patch --]
[-- Type: text/x-patch, Size: 613 bytes --]
--- mml.el.~1~ Sat May 11 08:52:50 2002
+++ mml.el Sun May 12 16:30:30 2002
@@ -540,7 +540,7 @@
(message-options-set 'message-sender sender))
(if (setq recipients (cdr (assq 'recipients cont)))
(message-options-set 'message-recipients recipients))
- (let ((style (mml-signencrypt-style (first encrypt-item))))
+ (let ((style (mml-signencrypt-style (first (or sign-item encrypt-item)))))
;; check if: we're both signing & encrypting, both methods
;; are the same (why would they be different?!), and that
;; the signencrypt style allows for combined operation.
[-- Attachment #2: Type: application/pgp-signature, Size: 239 bytes --]
next reply other threads:[~2002-05-12 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-12 14:39 Hans de Graaff [this message]
2002-05-13 15:20 ` Josh Huber
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=877km9ig6h.fsf@graaff.xs4all.nl \
--to=hans@degraaff.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).