From: joakim@verona.se
To: Ken Raeburn <raeburn@raeburn.org>
Cc: guile-devel@gnu.org
Subject: Re: ELisp?
Date: Sat, 12 Nov 2011 16:00:11 +0100 [thread overview]
Message-ID: <m3sjltbd38.fsf@chopper.vpn.verona.se> (raw)
In-Reply-To: <35C54F61-5144-4C54-808C-4A430F81D8D8@raeburn.org> (Ken Raeburn's message of "Fri, 11 Nov 2011 21:13:24 -0500")
Ken Raeburn <raeburn@raeburn.org> writes:
> On Nov 11, 2011, at 04:46, joakim@verona.se wrote:
>> Where is your public repository? I would be interested to have a look.
>
> Try git://raeburn.scripts.mit.edu/guile-emacs.git. But it's about two years old. :-(
> One of these days....
>
>> As a concrete example, one could use guiles libffi integration to offer
>> the same feature to Emacs. I could personally use it in my xwidgets
>> emacs branch to call dynamically into webkit rather than having to make
>> a c wrapper for each and every function.
>
> Hmm... this touches on a political issue I'd been avoiding thinking about. Namely, adding Guile to Emacs, with Guile's new FFI support, would make dynamically loading new executable code into Emacs easy, technically, including non-GPL code written specifically to extend Emacs. There's been a lot of resistance to that in the past. See for example http://lists.gnu.org/archive/html/emacs-devel/2003-07/msg00403.html .
Yes, this seems to have been resolved if the GCC scheme for identifying
GPL libraries is used. Basically GPL libraries expose a symbol declaring GPL compliance.
>
> On the technical side (ignoring the political/legal angles), I wonder if it would be quicker to drop FFI support into Emacs directly, using an interface based on the Guile one, and use that for now, until the Emacs+Guile work is far enough along to merge. I suspect your xwidgets code would be ready for integration much sooner than that. :-)
Quicker, yes, but less interesting. I suppose I'm looking for an excuse
to do this :)
> Ken
--
Joakim Verona
next prev parent reply other threads:[~2011-11-12 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 1:35 ELisp? Noah Lavine
2011-10-09 13:37 ` ELisp? joakim
2011-10-09 19:22 ` ELisp? Noah Lavine
2011-10-11 10:12 ` ELisp? Ken Raeburn
2011-11-11 9:46 ` ELisp? joakim
2011-11-12 2:13 ` ELisp? Ken Raeburn
2011-11-12 15:00 ` joakim [this message]
2011-11-13 0:56 ` ELisp? Ken Raeburn
2011-11-12 18:03 ` ELisp? Noah Lavine
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3sjltbd38.fsf@chopper.vpn.verona.se \
--to=joakim@verona.se \
--cc=guile-devel@gnu.org \
--cc=raeburn@raeburn.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 read-only IMAP folder(s) and NNTP newsgroup(s).