From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Encrypting outgoing message but not Gcc?
Date: Sun, 07 Dec 2003 10:16:45 -0500 [thread overview]
Message-ID: <m3smjw3bfm.fsf@asfast.com> (raw)
In-Reply-To: <m3vfos91x9.fsf@asfast.com>
[-- Attachment #1: Type: text/plain, Size: 666 bytes --]
Lloyd Zusman <ljz@asfast.com> writes:
> [ ... ]
>
> I was wondering why this option didn't work for me, and I found the code
> below in yesterday's CVS. Notice that it makes my user ID known to gpg
> by means of the `--remote-user' option. However, this option is no
> longer used in recent versions of gpg ... it's been replaced with
> `--recipient'.
>
> I think that we need a configuration variable that allows us to specify
> one or the other of these option flags, so that the code can be made to
> work with both older and newer versions of gpg.
Here's a patch for this. What do you folks think? If it's suitable,
feel free to apply it to CVS.
Thanks.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: recipient/remote-user option choice --]
[-- Type: text/x-patch, Size: 1025 bytes --]
*** pgg-gpg.el.orig Sun Dec 7 09:09:01 2003
--- pgg-gpg.el Sun Dec 7 10:11:05 2003
***************
*** 43,48 ****
--- 43,54 ----
:group 'pgg-gpg
:type '(repeat (string :tag "Argument")))
+ (defcustom pgg-gpg-recipient-arg "--recipient"
+ "Recipient option for gpg."
+ :group 'pgg-gpg
+ :type '(choice (const :tag "New `--recipient' option" "--recipient")
+ (const :tag "Old `--remote-user' option" "--remote-user")))
+
(defvar pgg-gpg-user-id nil
"GnuPG ID of your default identity.")
***************
*** 154,160 ****
(if recipients
(apply #'nconc
(mapcar (lambda (rcpt)
! (list "--remote-user" rcpt))
(append recipients
(if pgg-encrypt-for-me
(list pgg-gpg-user-id)))))))))
--- 160,166 ----
(if recipients
(apply #'nconc
(mapcar (lambda (rcpt)
! (list pgg-gpg-recipient-arg rcpt))
(append recipients
(if pgg-encrypt-for-me
(list pgg-gpg-user-id)))))))))
[-- Attachment #3: Type: text/plain, Size: 36 bytes --]
--
Lloyd Zusman
ljz@asfast.com
next prev parent reply other threads:[~2003-12-07 15:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-06 16:17 Lloyd Zusman
2003-12-06 16:46 ` Adam Sjøgren
2003-12-06 18:35 ` Lloyd Zusman
2003-12-07 1:54 ` Adam Sjøgren
2003-12-07 2:09 ` Lloyd Zusman
2003-12-07 2:25 ` Adam Sjøgren
2003-12-07 2:37 ` Lloyd Zusman
2003-12-07 11:07 ` Nathan Sullivan
2003-12-07 11:35 ` Adam Sjøgren
2003-12-07 13:08 ` Lloyd Zusman
2003-12-06 17:24 ` Reiner Steib
2003-12-06 17:58 ` Lloyd Zusman
2003-12-07 13:35 ` Lloyd Zusman
2003-12-07 13:45 ` Lloyd Zusman
2003-12-07 15:16 ` Lloyd Zusman [this message]
2003-12-07 15:44 ` Simon Josefsson
2003-12-07 16:28 ` Lloyd Zusman
2003-12-06 17:47 ` Simon Josefsson
2003-12-07 16:50 ` Lloyd Zusman
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=m3smjw3bfm.fsf@asfast.com \
--to=ljz@asfast.com \
/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).