Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: Hrvoje Niksic <hniksic@xemacs.org>
Subject: Re: Entering passphrase twice when sending PGP signed message
Date: Mon, 15 Sep 2003 01:15:10 +0200	[thread overview]
Message-ID: <ilu7k4bx8qp.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3llsrj7lm.fsf@defun.localdomain> (Jesper Harder's message of "Mon, 15 Sep 2003 01:03:33 +0200")

Jesper Harder <harder@myrealbox.com> writes:

> Simon Josefsson <jas@extundo.com> writes:
>
>> Hrvoje Niksic <hniksic@xemacs.org> writes:
>
> [`C-c C-m s o']
>
>>> Who ever came up with those key bindings??
>>
>> Can you find a better, unallocated, key binding, that doesn't
>> conflict with some mode that often can be enabled in message
>> buffers?
>
> Do it like forwarding, i.e. make an option for the default signing
> method.  Without a prefix `C-c C-m s' will use that, otherwise the
> numeric prefix selects which method to use.

Ah, I like it.  I guess the default should be PGP/MIME, and the rest
perhaps C-u 0 C-c C-m ? for PGP and C-u 1 C-c C-m ? for S/MIME?

OTOH, this is backward incompatible with a released version.

OTTH, how do this interact with the menu?  IIRC, you can't have the
menu item contain a key binding if it uses prefixes.  Perhaps Emacs
could be fixed in that regard though, there are several useful
operations that are invoked via prefixes that deserve proper menu
items.




  reply	other threads:[~2003-09-14 23:15 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-13 13:27 Hrvoje Niksic
2003-09-13 21:24 ` Simon Josefsson
2003-09-13 23:20   ` Hrvoje Niksic
2003-09-14  0:41     ` Simon Josefsson
2003-09-14  1:22       ` Hrvoje Niksic
2003-09-14 12:05         ` Simon Josefsson
2003-09-14 15:06           ` Hrvoje Niksic
2003-09-14 15:18             ` Simon Josefsson
2003-09-14 17:17               ` Hrvoje Niksic
2003-09-14 21:48                 ` Simon Josefsson
2003-09-14 23:03                   ` Jesper Harder
2003-09-14 23:15                     ` Simon Josefsson [this message]
2003-09-15  0:52                       ` Jesper Harder
2003-09-15 11:18                         ` Simon Josefsson
2003-10-17 18:03                         ` Lars Magne Ingebrigtsen
2003-10-17 21:44                           ` Simon Josefsson
2003-10-17 22:39                             ` Lars Magne Ingebrigtsen
2003-10-18  0:04                               ` Simon Josefsson
2003-10-18 15:49                           ` Jesper Harder
2003-10-18 16:26                             ` Lars Magne Ingebrigtsen
2005-10-13 19:48                             ` Attachments and security menu (was: Entering passphrase twice when sending PGP signed message) Reiner Steib
2006-04-26 20:30                               ` Attachments and security menu Reiner Steib
2003-09-14 21:02   ` Entering passphrase twice when sending PGP signed message Matthias Andree
2003-09-14 21:38     ` Simon Josefsson
2003-09-14 23:12       ` Matthias Andree
2003-09-14 23:49         ` Simon Josefsson
2003-09-15  0:10           ` Matthias Andree
2003-09-13 23:30 ` Jesper Harder
2003-09-14  1:17   ` Hrvoje Niksic
2003-09-14  1:45     ` Jesper Harder

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=ilu7k4bx8qp.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    --cc=hniksic@xemacs.org \
    /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).