From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Wherein I argue for the inclusion of libnettle in Emacs 24.5
Date: Thu, 06 Feb 2014 09:28:55 -0500 [thread overview]
Message-ID: <87ha8cco2g.fsf@lifelogs.com> (raw)
In-Reply-To: jwv8utoe6wk.fsf-monnier+emacs@gnu.org
On Thu, 06 Feb 2014 08:03:25 -0500 Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> He explained his objections earlier: against OpenPGP implementation,
>> prefers FFI, needs use cases.
SM> Good summary, indeed, thank you.
I promise I won't try to implement OpenPGP in the core. I may write an
ELPA package to do it. I may try to create "secret" strings in the
core, but I wouldn't even contemplate doing it without prior discussion
and review.
We have several use cases now, not just from me, posted in this thread.
I believe tight integration (at the C level, without FFI) will make
exploits against the encryption primitives less likely and will make
them more robust. I'm asking you to consider that GnuTLS might be a
valid exception to the general move to FFI because it's a facility, not
a feature.
>> In the past Emacs has rejected functionality because it was against the
>> goals of the FSF and the GNU project, not because it was deemed
>> amateurish.
SM> We do try to keep the core maintainable, which implies trying to keep
SM> "amateurish" code out of it. It also implies not adding stuff to it just
SM> so someone can play around with that new feature (tho it does happen,
SM> since it's always difficult to predict precisely how features will be
SM> used).
Right, I understand and sympathize.
I am asking for an exception, with the understanding that it won't
justify others, and with the justification that it's adding primitives
from a library we already include, because I think it will benefit users
and developers in the long run.
SM> But indeed, Elisp allows "amateurish" code, and we're happy to make it
SM> possible for amateurs to write their own code and get something useful
SM> from it. We all have to start somewhere.
Yes. In addition to the FSF and GNU goals, this creative freedom is
what makes Emacs great, IMHO.
Ted
next prev parent reply other threads:[~2014-02-06 14:28 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 22:36 Wherein I argue for the inclusion of libnettle in Emacs 24.5 Lars Ingebrigtsen
2014-02-04 3:21 ` Stefan Monnier
2014-02-04 13:07 ` Ted Zlatanov
2014-02-04 14:44 ` Stephen J. Turnbull
2014-02-04 18:36 ` Ted Zlatanov
2014-02-04 22:44 ` Lars Ingebrigtsen
2014-02-05 2:28 ` Stefan Monnier
2014-02-05 2:39 ` Lars Ingebrigtsen
2014-02-05 7:00 ` Ted Zlatanov
2014-02-05 8:13 ` Stephen J. Turnbull
2014-02-05 13:41 ` Ted Zlatanov
2014-02-05 15:50 ` andres.ramirez
2014-02-05 17:00 ` chad
2014-02-05 18:55 ` Ted Zlatanov
2014-02-06 5:03 ` Stephen J. Turnbull
2014-02-06 11:49 ` Ted Zlatanov
2014-02-06 13:03 ` Stefan Monnier
2014-02-06 14:28 ` Ted Zlatanov [this message]
2014-02-06 15:05 ` Stephen J. Turnbull
2014-02-06 15:54 ` Ted Zlatanov
2014-02-07 2:06 ` Stephen J. Turnbull
2014-02-07 6:51 ` David Kastrup
2014-02-07 7:15 ` Stephen J. Turnbull
2014-02-07 8:53 ` David Kastrup
2014-02-07 10:00 ` Stephen J. Turnbull
2014-02-07 10:49 ` David Kastrup
2014-02-07 20:43 ` Stephen J. Turnbull
2014-02-07 21:42 ` Ted Zlatanov
2014-02-07 22:23 ` Stephen J. Turnbull
2014-02-07 15:30 ` Ted Zlatanov
2014-02-07 9:07 ` Daiki Ueno
2014-02-07 11:54 ` Ted Zlatanov
2014-02-08 8:11 ` Daiki Ueno
2014-02-08 16:59 ` Ted Zlatanov
2014-02-05 8:19 ` Daiki Ueno
2014-02-04 13:10 ` Ted Zlatanov
2014-02-04 16:27 ` Paul Eggert
2014-02-04 18:32 ` Ted Zlatanov
2014-02-04 19:04 ` Paul Eggert
2014-02-04 20:11 ` Ted Zlatanov
2014-02-04 21:46 ` Paul Eggert
2014-02-04 22:44 ` Ted Zlatanov
2014-02-04 22:36 ` Lars Ingebrigtsen
2014-02-05 5:11 ` Daiki Ueno
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=87ha8cco2g.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.