From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: gpg.el: Signatures from trusted/untrusted keys?
Date: Mon, 30 Jul 2001 16:05:34 -0700 [thread overview]
Message-ID: <2nbsm2c91d.fsf@piglet.jia.vnet> (raw)
In-Reply-To: <E15RJGR-0000ep-00@dahaIM.dyndns.org> (Andreas Fuchs's message of "Mon, 30 Jul 2001 22:03:43 +0200")
Andreas Fuchs <asf@void.at> writes:
> Today, ShengHuo ZHU <zsh@cs.rochester.edu> wrote:
>> Does the patch for mml2015.el work with the old gpg.el (maybe losing
>> some features)? Since gpg.el is not officially maintained in the Gnus
>> CVS, I have to make sure that it doesn't break anything before adding
>> it.
>
> I fear not. It heavily depends on gpg being called with --status-fd set
> to 1 (or 2, if stderr isn't redirected, I didn't check).
>
> Hmm, I believe I can rewrite this patch as a seperate .el which just
> overwrites mml2015-gpg-extract-from (advice is out of the question, I
> think) and sets the variables to the right values.
I've installed the patch with minor modifications.
> Another thing this patch does is move some of gpg's status messages into
> the info text of the mml buttons (for example "Quit." is displayed
> instead of "Failed." in the button text). This does not depend on any
> changes outside of mml2015.el.
Thanks.
> Another thing that I would like to know: What is the opinion of you
> people on having a two-line info text on a mime button? I mean buttons
> like:
>
> [[PGP Signed Part:Foo Bar <foo@bar.org>
> Untrusted, Fingerprint: XXXX YYYY XXXX YYYY XXXX YYYY XXXX YYYY]]
Fine for me.
ShengHuo
next prev parent reply other threads:[~2001-07-30 23:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 8:19 Andreas Fuchs
2001-07-30 9:28 ` Andreas Fuchs
2001-07-30 9:58 ` Nuutti Kotivuori
2001-07-30 14:52 ` Andreas Fuchs
2001-07-30 19:37 ` ShengHuo ZHU
2001-07-30 20:03 ` Andreas Fuchs
2001-07-30 22:35 ` Kai Großjohann
2001-08-04 15:35 ` Florian Weimer
2001-07-30 23:05 ` ShengHuo ZHU [this message]
2001-08-01 19:40 ` Andreas Fuchs
2001-08-01 21:57 ` ShengHuo ZHU
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=2nbsm2c91d.fsf@piglet.jia.vnet \
--to=zsh@cs.rochester.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).