From: Josh Huber <huber@alum.wpi.edu>
Subject: message-options-get problem...
Date: 12 Jun 2001 14:46:07 -0400 [thread overview]
Message-ID: <87zobdk040.fsf@mclinux.com> (raw)
I wonder what's going on here.
A friend of mine whom I regularly send encrypted email told me today
my mail wasn't also signed. I think I've (finally) tracked down where
the problem is happening.
in mml2015-gpg-encrypt, there is this block:
(or
(message-options-get 'message-recipients)
(message-options-set 'message-recipients
(read-string "Recipients: ")))
which is used to extract the recipients of the message, and passed
along down the chain of calls ultimately to gpg. The problem is that
message-options-get is returning an array with one *extra* item, an
empty string.
so (when testing, inserting (debug) at appropriate places), I noticed
that mail addressed to myself would return the list
("huber@alum.wpi.edu" ""), which finally got translated into:
gpg .... -r huber@alum.wpi.edu -r --sign ...
^^^^^^^^^
there is the problem...anyone have any ideas as to why message is
returning a bogus empty string at the end of the list?
I'll keep looking, but I thought someone else might have a hint.
Thanks,
--
Josh Huber
reply other threads:[~2001-06-12 18:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87zobdk040.fsf@mclinux.com \
--to=huber@alum.wpi.edu \
/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).