From: "Richard M. Stallman" <rms@gnu.org>
To: David Hansen <david.hansen@gmx.net>
Cc: emacs-devel@gnu.org
Subject: Re: An Emacs plug-in for a browser (Firefox?)
Date: Sun, 07 Sep 2008 19:36:18 -0400 [thread overview]
Message-ID: <E1KcTnm-0006Uw-R3@fencepost.gnu.org> (raw)
In-Reply-To: <87zlml7y8v.fsf@localhorst.mine.nu> (message from David Hansen on Sat, 06 Sep 2008 23:36:32 +0200)
Joakim wrote a patch that allows him to display arbitrary GTK Widgets in
a buffer.
That is a useful feature because it could be used to implement various
GTK-style interfaces for Emacs package.
This could either be used to directly link Emacs against the
Gecko or WebKit GTK Widget, or to use the special GTK widget "GtkPlug"
which embeds an application capable of the XEmbed protocol.
For modularity's sake, it is much cleaner to run the browser in a
separate process and have it display thru GtkPlug. To link Emacs with
Gecko or Webkit would be a lot of extra trouble, and the trouble would
go on and on.
Someone mentioned that it would be really cool to access all the DOM
stuff from Emacs Lisp.
What uses would this be good for, if it existed?
You could write nice filter for the web, e.g. remove ads, filter cookies
or change images of your president to "hello.jpg".
If what you want is extensibility in Lisp for your web browser, I
think it is better to interface Guile (rather than Emacs) to the
browser. Emacs is not just Lisp, it is certain model of textual data.
Web browsers have a different model of textual data, and trying to
glue them together would produce a gross kludge.
next prev parent reply other threads:[~2008-09-07 23:36 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
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 [this message]
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=E1KcTnm-0006Uw-R3@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=david.hansen@gmx.net \
--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).