From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: pgg: mml-secure-encrypt-pgpmime with wrong keybinding?
Date: Mon, 28 Oct 2002 19:56:34 -0500 [thread overview]
Message-ID: <874rb6dpvh.fsf@mail.paradoxical.net> (raw)
In-Reply-To: <smyqp3x2.fsf@ID-23066.news.dfncis.de>
clemens fischer <ino@despammed.com> writes:
> just updated oort-gnus from CVS yesterday, but my problem remains. i
> have the following keybindings:
>
> C-c RET C s mml-secure-encrypt-smime
> C-c RET C o mml-secure-encrypt-pgp
> C-c RET C p mml-secure-encrypt-pgpmime
>
> C-c RET S s mml-secure-message-sign-smime
> C-c RET S o mml-secure-message-sign-pgp
> C-c RET S p mml-secure-message-sign-pgpmime
>
> but the upper three of them make #part's, not #secure's. the correct
> equivalents mml-secure-message-encrypt-pgpmime et.al. exist and work,
> but the key bindings are wrong.
>
> i do load the gnus-cookies by `(load "gnus-load.el")' at the top of my
> ~/.gnus, so where is the failure?
Looks like someone made a typo in mml.el when adding the signpart and
encryptpart keymaps.
I just checked in a fix.
--
Josh Huber
next prev parent reply other threads:[~2002-10-29 0:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 22:57 clemens fischer
2002-10-29 0:56 ` Josh Huber [this message]
2002-11-02 0:31 ` Clemens Fischer
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=874rb6dpvh.fsf@mail.paradoxical.net \
--to=huber@alum.wpi.edu \
--cc=huber+dated+1036284504.94521a@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).