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: Tue, 04 Feb 2014 15:11:37 -0500 [thread overview]
Message-ID: <87a9e6eiyu.fsf@lifelogs.com> (raw)
In-Reply-To: 52F139D3.3030401@cs.ucla.edu
On Tue, 04 Feb 2014 11:04:51 -0800 Paul Eggert <eggert@cs.ucla.edu> wrote:
PE> On 02/04/2014 10:32 AM, Ted Zlatanov wrote:
PE> Using the GnuTLS API would remove Stefan's objection to the change,
PE> no? Emacs already depends on the GnuTLS API.
>>
>> No, sadly, because it's new C glue code and his goal is to remove such.
PE> As I understand it his objection is to adding dependencies on new
PE> libraries, not to more-effectively using libraries that Emacs already
PE> depends on. For example, he didn't object to adding
PE> internal-default-process-filter or to bool-vector-count-population,
PE> even though these functions both involved new C glue code.
Well, here's the rejection letter:
http://permalink.gmane.org/gmane.emacs.devel/163980
As I said then, feel free to add your vote of support. So far Lars and
I are the only ones asking for encryption that doesn't require calling
out to external binaries like GnuPG. I followed up to Lars specifically
so I could explain that I thought (after a few months of letting things
rest) that loose coupling of *encryption* features specifically was a
bad idea. Compared to, say, XML parsing, encryption is much less of a
feature and more of an integral facility.
I respect and understand Stefan's opinion and have not argued about the
FFI in general (in fact I was planning to work on it; it's a neat
feature), but I think Lars makes good points against FFI from practical
experience, and I think my point above is worth considering as well.
Ted
next prev parent reply other threads:[~2014-02-04 20:11 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a9e6eiyu.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).