From: Simon Josefsson <jas@extundo.com>
Subject: Re: gpg-ring.el/gpg.el?
Date: Fri, 16 Nov 2001 22:37:17 +0100 [thread overview]
Message-ID: <iluadxmwg6q.fsf@dhcp128.extundo.com> (raw)
In-Reply-To: <87lmh6ifck.fsf@mclinux.com> (Josh Huber's message of "Fri, 16 Nov 2001 16:19:07 -0500")
Josh Huber <huber@alum.wpi.edu> writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> FSF doesn't have papers for it.
>
> Bummer, is the author going to do it, or what?
I think lawyers are involved.
>> C-c C-m c p encrypts the current MIME part. If you C-c C-m c p on a
>> multipart part, the entire multipart is encrypted.
>
> Yes, I realize this. What I'm suggesting is that there should be a
> key bound which inserts <$multipart ...> if there are other parts, or
> just <$part ...> if there are not. It would prevent accidental
> unencrypted traffic...that's all.
>
> I know, this is a small piece of lisp :)
The default commands should probably do what you suggest, instead of
the current less intuitive thing.
next prev parent reply other threads:[~2001-11-16 21:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 19:10 gpg-ring.el/gpg.el? Josh Huber
2001-11-16 20:32 ` gpg-ring.el/gpg.el? Simon Josefsson
2001-11-16 21:19 ` gpg-ring.el/gpg.el? Josh Huber
2001-11-16 21:37 ` Simon Josefsson [this message]
2001-11-17 11:10 ` gpg-ring.el/gpg.el? Florian Weimer
2001-11-17 11:43 ` gpg-ring.el/gpg.el? Simon Josefsson
2001-11-19 21:56 ` gpg-ring.el/gpg.el? Florian Weimer
2001-11-20 20:51 ` gpg-ring.el/gpg.el? Werner Koch
2001-11-16 21:38 ` gpg-ring.el/gpg.el? Matt Armstrong
2001-11-19 15:03 ` gpg-ring.el/gpg.el? Josh Huber
2001-11-19 19:18 ` gpg-ring.el/gpg.el? Matt Armstrong
2001-11-19 19:43 ` gpg-ring.el/gpg.el? Josh Huber
2001-11-19 20:05 ` gpg-ring.el/gpg.el? Matt Armstrong
2001-11-20 20:32 ` gpg-ring.el/gpg.el? Jack Twilley
2001-11-21 15:05 ` gpg-ring.el/gpg.el? 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=iluadxmwg6q.fsf@dhcp128.extundo.com \
--to=jas@extundo.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).