Gnus development mailing list
 help / color / mirror / Atom feed
From: Jens Lechtenboerger <jens.lechtenboerger@fsfe.org>
To: ding@gnus.org
Cc: Daiki Ueno <ueno@gnu.org>
Subject: Re: Refactoring of mml1991.el, mml2015.el, mml-smime.el
Date: Sat, 07 Nov 2015 21:28:21 +0100	[thread overview]
Message-ID: <87io5d7dwa.fsf@informationelle-selbstbestimmung-im-internet.de> (raw)
In-Reply-To: <m3vb9fvpww.fsf-ueno@gnu.org>

On 2015-11-06, at 11:10, Daiki Ueno wrote:

> Jens Lechtenboerger <jens.lechtenboerger@fsfe.org> writes:
>
>> On 2014-09-21, at 12:08, Jens Lechtenboerger wrote:

>> In my code, each pair is replaced with a single variable with the prefix
>> “mml-epg-openpgp”, e.g., “mml-epg-openpgp-cache-passphrase”.
>>
>> Concerning S/MIME, I introduced the same variables with prefix
>> “mml-epg-smime”.
>
> The prefix "mml-epg" sounds a bit too much implementation detail.  How
> about renaming those prefixes to mml{,-secure}-pgpmime /
> mml{,-secure}-smime and moving to mml-sec.el?
>
> (I would use the word "pgpmime" to distinguish PGP/MIME signatures from
> inline PGP signatures.  I remember there is already a use of the word in
> Gnus).

Yes, I can move that to mml-sec.el.  However, note that I’m not
restricting functionality to pgpmime.  Inline PGP is still available
(via mml1991.el).  The variables whose names include “openpgp” in my
code cover pgpmime (mml2015.el) as well as inline PGP (mml1991.el).
Therefore, I’d like to use “openpgp” instead of “pgpmime”.

Moreover, in mml-sec.el the variables mml-secure-cache-passphrase
and mml-secure-passphrase-cache-expiry are defined, which have
specialized versions in mml-smime.el, mml1991.el, and mml2015.el,
which I meant to delete or to supersede by two new variables (for
OpenPGP and S/MIME).  So far, I didn’t receive strong feedback on
the related issue of my e-mail (passphrase caching in Emacs vs
gpg-agent).  Now I wonder whether to get rid of all of them except
those in mml-secure.el (with a recommendation to use gpg-agent).

How should I proceed from here?  Ask for opinions on other mailing
lists such as the following two?
https://lists.gnu.org/mailman/listinfo/info-gnus-english
https://lists.gnu.org/mailman/listinfo/help-gnu-emacs

> I saw a few functions prefixed with "jl-".  Maybe they can be moved to
> mm-util.el or gnus-util.el?

Indeed, gnus-util.el seems appropriate.

Best wishes
Jens



  reply	other threads:[~2015-11-07 20:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-21 10:08 Default encryption for Message Jens Lechtenboerger
2014-09-23 20:02 ` Ted Zlatanov
2014-09-24 13:59   ` Jens Lechtenboerger
2014-09-24 15:28     ` Ted Zlatanov
2014-09-24  2:23 ` Daiki Ueno
2014-09-24 14:30   ` Jens Lechtenboerger
2014-09-25  3:06     ` Daiki Ueno
2014-09-25 16:18       ` Jens Lechtenboerger
2014-09-28  0:16         ` Daiki Ueno
2014-10-02 16:51           ` Jens Lechtenboerger
2015-10-16 16:26 ` Refactoring of mml1991.el, mml2015.el, mml-smime.el (was: Default encryption for Message) Jens Lechtenboerger
2015-10-18  7:36   ` Refactoring of mml1991.el, mml2015.el, mml-smime.el Peter Münster
2015-10-18 14:09   ` Greg Troxel
2015-10-19 12:58     ` Jens Lechtenboerger
2015-11-06  2:10   ` Daiki Ueno
2015-11-07 20:28     ` Jens Lechtenboerger [this message]
2015-11-11  6:20       ` Daiki Ueno
2015-11-14 15:44         ` Jens Lechtenboerger
2015-11-20 16:31           ` in defense of GitLab or something (was: Refactoring of mml1991.el, mml2015.el, mml-smime.el) Ted Zlatanov

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=87io5d7dwa.fsf@informationelle-selbstbestimmung-im-internet.de \
    --to=jens.lechtenboerger@fsfe.org \
    --cc=ding@gnus.org \
    --cc=ueno@gnu.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).