From: Phil Jackson <phil@shellarchive.co.uk>
To: joakim@verona.se
Cc: Paul Michael Reilly <pmr@pajato.com>,
raman@users.sourceforge.net, emacs-devel@gnu.org
Subject: Re: An Emacs plug-in for a browser (Firefox?)
Date: Fri, 05 Sep 2008 09:53:18 +0100 [thread overview]
Message-ID: <87zlmnezy9.fsf@shellarchive.co.uk> (raw)
In-Reply-To: <m31vzz6qi7.fsf@verona.se> (joakim@verona.se's message of "Fri, 05 Sep 2008 08:44:32 +0200")
joakim@verona.se writes:
>> And this approach would appear to have a platform independent nature,
>> highly appealing. I don't know anything about Webkit. Are you
>> talking about adding Webkit to the C level of Emacs, doing an Emacs
>> Lisp binding to Webkit (probably running in a separate process or
>> mulitple processes ala Chrome) or something else?
>
> It's somewhat possible to do this already. I mailed a patch to
> emacs-devel some time ago that lets Emacs embed gtk widgets in a
> buffer, like images. (Its very alpha but shows that its possible, at
> least)
So, out of interest, how would a Javascript engine (if any) and elisp
co-exist in any sort of harmony?
Cheers,
Phil
--
Philip Jackson
http://www.shellarchive.co.uk
next prev parent reply other threads:[~2008-09-05 8:53 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 22:18 An Emacs plug-in for a browser (Firefox?) Paul Michael Reilly
2008-09-05 0:16 ` David De La Harpe Golden
2008-09-05 0:19 ` David House
2008-09-05 2:42 ` T. V. Raman
2008-09-05 4:53 ` Paul Michael Reilly
2008-09-05 6:44 ` joakim
2008-09-05 8:53 ` Phil Jackson [this message]
2008-09-05 9:21 ` joakim
2008-09-05 9:30 ` Lennart Borgman (gmail)
2008-09-05 11:20 ` Antoine Levitt
2008-09-06 7:12 ` Richard M. Stallman
2008-09-06 10:48 ` Antoine Levitt
2008-09-06 21:04 ` Richard M. Stallman
2008-09-06 21:36 ` David Hansen
2008-09-06 21:49 ` Lennart Borgman (gmail)
2008-09-06 22:25 ` David Hansen
2008-09-06 22:48 ` Lennart Borgman (gmail)
2008-09-06 23:08 ` David Hansen
2008-09-06 22:41 ` Sean O'Rourke
2008-09-07 23:36 ` Richard M. Stallman
2008-09-06 16:42 ` Chong Yidong
2008-09-06 16:58 ` joakim
2008-09-06 19:42 ` Chong Yidong
2008-09-06 20:20 ` David Hansen
2008-09-06 21:54 ` T. V. Raman
2008-09-06 20:11 ` Stefan Monnier
2008-09-07 17:39 ` Richard M. Stallman
2008-09-07 17:49 ` Lennart Borgman (gmail)
2008-09-07 18:29 ` Chong Yidong
2008-09-08 9:22 ` Richard M. Stallman
2008-09-08 12:31 ` Chong Yidong
2008-09-08 17:07 ` Antoine Levitt
2008-09-08 19:05 ` Thomas Lord
2008-09-08 19:07 ` Antoine Levitt
2008-09-08 20:27 ` Thomas Lord
2008-09-08 20:34 ` Stefan Monnier
2008-09-08 21:33 ` joakim
2008-09-08 21:46 ` Thomas Lord
2008-09-09 8:11 ` Richard M. Stallman
2008-09-08 22:13 ` Richard M. Stallman
2008-09-07 19:55 ` Stefan Monnier
2008-09-08 9:22 ` Richard M. Stallman
2008-09-05 13:33 ` T. V. Raman
2008-09-05 13:32 ` T. V. Raman
2008-09-05 20:40 ` Christian Faulhammer
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=87zlmnezy9.fsf@shellarchive.co.uk \
--to=phil@shellarchive.co.uk \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
--cc=pmr@pajato.com \
--cc=raman@users.sourceforge.net \
/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).