From: Daiki Ueno <ueno@gnu.org>
To: ding@gnus.org
Subject: Re: Refactoring of mml1991.el, mml2015.el, mml-smime.el
Date: Fri, 06 Nov 2015 11:10:23 +0900 [thread overview]
Message-ID: <m3vb9fvpww.fsf-ueno@gnu.org> (raw)
In-Reply-To: <87k2qmsrt1.fsf@informationelle-selbstbestimmung-im-internet.de> (Jens Lechtenboerger's message of "Fri, 16 Oct 2015 18:26:34 +0200")
Jens Lechtenboerger <jens.lechtenboerger@fsfe.org> writes:
> On 2014-09-21, at 12:08, Jens Lechtenboerger wrote:
>
>> 5. Refactoring
>> mml1991.el, mml2015.el, and mml-smime.el share code, forcing
>> copy-and-paste on updates.
>
> Hi there,
>
> this is a continuation of a one year old thread. Sorry for the delay.
> Essentially, I proposed a refactoring of mml1991.el, mml2015.el, and
> mml-smime.el such that common code can be maintained in a single file.
Thanks for working on that. I am afraid I don't have time at the moment
to go through the patch, but maybe you can go ahead and we could fix it
later on if any problem arises?
> 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).
> A tarball with my files is available over there (README.txt explains its
> contents):
> http://informationelle-selbstbestimmung-im-internet.de/emacs/mml-epg-2015-10-16.tar.bz2
> http://informationelle-selbstbestimmung-im-internet.de/emacs/mml-epg-2015-10-16.tar.bz2.asc
I saw a few functions prefixed with "jl-". Maybe they can be moved to
mm-util.el or gnus-util.el?
Thanks,
--
Daiki Ueno
next prev parent reply other threads:[~2015-11-06 2:10 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 [this message]
2015-11-07 20:28 ` Jens Lechtenboerger
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=m3vb9fvpww.fsf-ueno@gnu.org \
--to=ueno@gnu.org \
--cc=ding@gnus.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).