Mark D. Baushke | 1 Oct 18:17 2003
X-Face
Picon

Re: mml-pgpmime-sign-buffer vs mml-pgp-sign-buffer


Satyaki Das <satyakid <at> stanford.edu> wrote:

> Mark D. Baushke <mdb <at> gnu.org> wrote:
> 
> > Satyaki Das <satyakid <at> stanford.edu> writes:
> > 
> > > I was going to suggest that we set up things so that with a
> > > prefix arg "C-c C-m C-s" should prompt the user for the type of
> > > signature to use. But turns out the prefix arg is already used to
> > > remove the signature directive. Is that really useful? 
> > 
> > Yes, it is useful to be able to change your mind and NOT sign or encrypt
> > a particular message.
> 
> I was thinking that the user can easily achieve this by going to
> the directive and using C-k to delete it. The question is do you
> often change your mind about signing something?

If it is an automagic part of the identity? It seems to run to about 40%
of the time for me so far. I'll note that the mml.el file has a single
menu item:

    ["Encrypt/Sign off"         mml-unsecure-message mh-gnus-pgp-support-flag]

for all of their various modes.

> Also, if we have separate key bindings for the different kinds
> of signatures, then we will have multiple key bindings that remove
> the message signing directive.
(Continue reading)

Mark D. Baushke | 1 Oct 20:00 2003
X-Face
Picon

PGP related key bindings and menus

Hi Folks,

I am not sure I like all of the key bindings I created.
Let me know what you think of the following patch.

	Thanks,
	-- Mark

Log message:
2003-10-01  Mark D Baushke  <mdb <at> gnu.org>

	* mh-mime.el (mh-secure-message): New function used to generate
	the mml security tags.
	(mh-mml-unsecure-message): Wrapper around mml-unsecure-messages.
	(mh-mml-secure-message-sign-pgpmime): Use mh-secure-message.
	(mh-mml-secure-message-encrypt-pgpmime): Ditto.
	(mh-mml-secure-message-encrypt-pgp): New function.
	(mh-mml-secure-message-encrypt-smime): Ditto.
	(mh-mml-secure-message-onlyencrypt-pgp): Ditto.
	(mh-mml-secure-message-onlyencrypt-pgpmime): Ditto.
	(mh-mml-secure-message-onlyencrypt-smime): Ditto.
	(mh-mml-secure-message-sign-pgp): Ditto.
	(mh-mml-secure-message-sign-smime): Ditto.

	* mh-comp.el (mh-letter-menu, mh-letter-mode-help-messages,
	(mh-letter-mode-map): Update to use new functions.

Index: mh-comp.el
===================================================================
RCS file: /cvsroot/mh-e/src/mh-comp.el,v
(Continue reading)

Satyaki Das | 1 Oct 20:19 2003
Face
Picon

Re: PGP related key bindings and menus

Mark D. Baushke <mdb <at> gnu.org> writes:

> Hi Folks,
> 
> I am not sure I like all of the key bindings I created.
> Let me know what you think of the following patch.

Since you have already added a separate key binding for
mh-mml-unsecure-message, I suggest that we have only one key
binding to sign. It defaults to one of the methods (this should
be customizable), and with a prefix it will prompt for the
signing method.

I think most users will be using only one of the methods most of
the time and very infrequently the others. So it is very likely
they won't remember the key binding for the infrequently used
methods if we have different keys for each function. Also, the
most common case would have a short key binding.

For the menu, I wonder if we can have nested menus.

Satyaki

Mark D. Baushke | 1 Oct 22:29 2003
X-Face
Picon

Re: PGP related key bindings and menus

Satyaki Das <satyakid <at> stanford.edu> writes:

> Mark D. Baushke <mdb <at> gnu.org> writes:
> 
> > Hi Folks,
> > 
> > I am not sure I like all of the key bindings I created.
> > Let me know what you think of the following patch.
> 
> Since you have already added a separate key binding for
> mh-mml-unsecure-message, I suggest that we have only one key
> binding to sign. It defaults to one of the methods (this should
> be customizable), and with a prefix it will prompt for the
> signing method.

There are four states:

      do not sign, do not encrypt
      only sign
      only encrypt
      sign and encrypt

I will grant you that the three methods probably could be set
with a defcustom. Part of the reason for problems with the menu
was getting the distinction between sign+encrypt and encrypt.

> I think most users will be using only one of the methods most of
> the time and very infrequently the others. So it is very likely
> they won't remember the key binding for the infrequently used
> methods if we have different keys for each function. Also, the
(Continue reading)

Peter S Galbraith | 2 Oct 02:13 2003
Picon

Re: PGP related key bindings and menus

Mark D. Baushke <mdb <at> gnu.org> wrote:

> Satyaki Das <satyakid <at> stanford.edu> writes:
> 
> > Mark D. Baushke <mdb <at> gnu.org> writes:
> > 
> > > Hi Folks,
> > > 
> > > I am not sure I like all of the key bindings I created.
> > > Let me know what you think of the following patch.
> > 
> > Since you have already added a separate key binding for
> > mh-mml-unsecure-message, I suggest that we have only one key
> > binding to sign. It defaults to one of the methods (this should
> > be customizable), and with a prefix it will prompt for the
> > signing method.

I agree.

> There are four states:
> 
>       do not sign, do not encrypt
>       only sign
>       only encrypt
>       sign and encrypt
> 
> I will grant you that the three methods probably could be set
> with a defcustom. Part of the reason for problems with the menu
> was getting the distinction between sign+encrypt and encrypt.
> 
(Continue reading)

Bill Wohler | 2 Oct 04:43 2003
Picon
Picon

Re: PGP related key bindings and menus

Peter S Galbraith <p.galbraith <at> globetrotter.net> wrote:

> > > For the menu, I wonder if we can have nested menus.
> > 
> > I have no idea how to do that.
> 
> Easy:
> 
> (easy-menu-define
>   mh-letter-menu mh-letter-mode-map "Menu for MH-E letter mode."
>   '("Letter"
>     ["Send This Draft"          mh-send-letter t]
> ...
>     ["Insert Signature"         mh-insert-signature t]
>     ("Sign"
>       ["GPG Sign message"
>        mh-mml-secure-message-sign-pgpmime mh-gnus-pgp-support-flag]
> ...

Thanks Peter, I figured you'd chip in.

Since all of the menu items start with PGP... I'd suggest naming the
menu PGP and then dropping PGP from each of the child menu item names.

Rest assured that this will all be fine-tuned when I hit that portion of
the manual ;-).

--

-- 
Bill Wohler <wohler <at> newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
(Continue reading)

Bill Wohler | 2 Oct 04:58 2003
Picon
Picon

Re: PGP related key bindings and menus

Mark D. Baushke <mdb <at> gnu.org> wrote:

> Index: mh-comp.el
> ===================================================================
> RCS file: /cvsroot/mh-e/src/mh-comp.el,v
> retrieving revision 1.264
> diff -u -p -r1.264 mh-comp.el
> --- mh-comp.el	23 Sep 2003 20:20:31 -0000	1.264
> +++ mh-comp.el	1 Oct 2003 17:57:48 -0000
>  <at>  <at>  -793,10 +793,20  <at>  <at>  Returns t if found, nil if not."
>      ["Yank Current Message"     mh-yank-cur-msg t]
>      ["Insert a Message..."      mh-insert-letter t]
>      ["Insert Signature"         mh-insert-signature t]
> -    ["GPG Sign message"
> +    ["PGP Sign message"

That should be "PGP Sign Message". Ditto for the others. You followed a
bad example ;-).

However, as discussed in a previous message, we'll have a PGP menu so
the menu item will be actual "Sign Message".

> +    ["PGP/MIME Sign message"

I saw MIME in parenthesis elsewhere, so I guess this would become "Sign
Message (MIME)".

> +    ["PGP Sign+Encrypt message"
> +     mh-mml-secure-message-encrypt-pgp mh-gnus-pgp-support-flag]
> +    ["PGP/MIME Sign+Encrypt message"
(Continue reading)

SourceForge.net | 2 Oct 05:29 2003
Picon
Picon

[ mh-e-Bugs-802720 ] Set Content-Type of .vcf files to text/x-vcard

Bugs item #802720, was opened at 2003-09-08 16:18
Message generated for change (Comment added) made by psg
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=113357&aid=802720&group_id=13357

>Category: Documentation
>Group: CVS
Status: Open
>Resolution: Fixed
Priority: 5
Submitted By: Bill Wohler (wohler)
>Assigned to: Bill Wohler (wohler)
Summary: Set Content-Type of .vcf files to text/x-vcard

Initial Comment:
We need to recognize that a .vcf file is of type

text/x-vcard. This is needed to generate the right

Content-Type when using "C-c C-m TAB" to insert a vcard.

----------------------------------------------------------------------

>Comment By: Peter S Galbraith (psg)
Date: 2003-10-01 23:29

Message:
Logged In: YES 
user_id=31877

(Continue reading)

Mark D. Baushke | 2 Oct 09:41 2003
X-Face
Picon

Re: PGP related key bindings and menus

Bill Wohler <wohler <at> newt.com> writes:

> Mark D. Baushke <mdb <at> gnu.org> wrote:
> 
> > Index: mh-comp.el
> > ===================================================================
> > RCS file: /cvsroot/mh-e/src/mh-comp.el,v
> > retrieving revision 1.264
> > diff -u -p -r1.264 mh-comp.el
> > --- mh-comp.el	23 Sep 2003 20:20:31 -0000	1.264
> > +++ mh-comp.el	1 Oct 2003 17:57:48 -0000
> >  <at>  <at>  -793,10 +793,20  <at>  <at>  Returns t if found, nil if not."
> >      ["Yank Current Message"     mh-yank-cur-msg t]
> >      ["Insert a Message..."      mh-insert-letter t]
> >      ["Insert Signature"         mh-insert-signature t]
> > -    ["GPG Sign message"
> > +    ["PGP Sign message"
> 
> That should be "PGP Sign Message". Ditto for the others. You followed a
> bad example ;-).
> 
> However, as discussed in a previous message, we'll have a PGP menu so
> the menu item will be actual "Sign Message".
> 
> > +    ["PGP/MIME Sign message"
> 
> I saw MIME in parenthesis elsewhere, so I guess this would become "Sign
> Message (MIME)".
> 
> > +    ["PGP Sign+Encrypt message"
(Continue reading)

Peter S Galbraith | 2 Oct 15:05 2003
Picon

Re: PGP related key bindings and menus

Mark D. Baushke <mdb <at> gnu.org> wrote:

> > However, we could make this problem go away if we could have little
> > checkboxes next to each menu item (as in the Options menu item) so that
> > the menu item to turn them off explicitly isn't needed.
> 
> Examples please?

     ["Name in menu" (toggle-function-to-call)
      :style toggle :active variable-that-says-if-we-have-this-feature-flag
      :selected (function-to-tell-to-currently-set-or-unset)]

So you need a function to toggle it (insert and remove the stuff), a
function to detect if the stuff is insertred, and optionally a function
or variable to return if the feature is available in the first place (if
not, the buttom is grayed out).

Peter


Gmane