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 13:18:53 +0200	[thread overview]
Message-ID: <iluu17ewb8i.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m365jukh3s.fsf@defun.localdomain> (Jesper Harder's message of "Mon, 15 Sep 2003 02:52:55 +0200")

Jesper Harder <harder@myrealbox.com> writes:

> Simon Josefsson <jas@extundo.com> writes:
>
>> Jesper Harder <harder@myrealbox.com> writes:
>>
>>> 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.
>
> Yeah, but you could argue that it's better to change it now before
> Oort Gnus has been bundled with a released version of Emacs.

Yes.  And it is not like hitting the old combination would exit emacs,
so people would notice and recover.

>> OTTH, how do this interact with the menu?  IIRC, you can't have the
>> menu item contain a key binding if it uses prefixes.
>
> I don't think we necessarily need menu items for the prefixes -- a
> sub-menu which let's you change the default with radio buttons would
> be better, IMHO.
>
> I think it's a great opportunity to simplify and clean up the
> crypto-related menu items.  We could arrange it like this (which would
> make the Attachments menu much less crowded):
>
>     +---------------------------------+
>     | Sign                (C-c RET s) |
>     | Encrypt             (C-c RET c) |
>     | Sign Part           (C-c RET S) |
>     | Encrypt Part        (C-c RET C) |
>     | Encrypt/Sign Off  (C-c RET C-n) |
>     | Change Security Method     +-----------------------+
>     +----------------------------|  [x] PGP/MIME         |
>                                  |  [ ] Traditional PGP  |
>                                  |  [ ] S/MIME           |
>                                  +-----------------------+

While it looks simpler and better, I'm not so sure.  A look at my own
signed/encrypted communication patterns gives roughly:

   50 % PGP
   40 % PGP/MIME
   10 % S/MIME

So I would have a hard time choosing PGP/MIME or PGP as the default,
and I would have to change it frequently.  And I do use the menubar,
since the keybindings are obscure, and entering the MML tag manually
is boring.  I suspect this is not a corner situation, traditional PGP
is still the norm if you want to talk with non-technical savvy people.

Although, I could use PGP/MIME as the default and manully change
'pgpmime' to 'pgp' in the MML tag.  Hm.

Speaking generally: The Gnus menubar are rather long and unfriendly.
One almost get the impression that they were designed by putting
everything that has a key binding into the menu.  Perhaps we could
have simplified and user friendly menus (like what you propose) in the
top-level menu by default, and an Advanced sub-menu that contains all
possible commands.  OTOH moving things around is also bad, and placing
lots of entries in a submenu can look weird.  O well, just an idea.




  reply	other threads:[~2003-09-15 11:18 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
2003-09-15  0:52                       ` Jesper Harder
2003-09-15 11:18                         ` Simon Josefsson [this message]
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=iluu17ewb8i.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).