From: "Antoine Levitt" <smeuuh@gmail.com>
To: rms@gnu.org
Cc: pmr@pajato.com, lennart.borgman@gmail.com, joakim@verona.se,
emacs-devel@gnu.org, raman@users.sourceforge.net,
phil@shellarchive.co.uk
Subject: Re: An Emacs plug-in for a browser (Firefox?)
Date: Sat, 6 Sep 2008 12:48:09 +0200 [thread overview]
Message-ID: <6fa54e4e0809060348l2ca36872u2445d0824960021b@mail.gmail.com> (raw)
In-Reply-To: <E1Kbrxw-0006mU-23@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1577 bytes --]
2008/9/6 Richard M. Stallman <rms@gnu.org>
> To make Emacs display web pages with their correct appearance is a
> gigantic job. I don't think that linking Emacs with a web browser
> display engine is a feasible method.
Why not ? See this thread :
http://lists.gnu.org/archive/html/emacs-devel/2008-05/msg00456.html
He already embeds emacs within emacs. Embedding firefox (or chrome, or
midori, or whatever) shouldn't be much harder. A keymap would be transfered
to the underlying process (kinda like what term-mode does), so the user can
scroll the window and thinkgs like that. That alone would be extremely
useful. Then, we can use inter-process communication (maybe mozrepl can do
that ?) to better communicate with the browser (and really integrate it into
emacs, ie have the minibuffer prompt the user for the webpage to go to, and
maybe add link following, kind of like how conkeror does). What I think
would be really hard to do is have emacs edit text areas in place, but
that's only icing on the cake.
>
> I proposed years ago that we extend Emacs to the point where it can
> function as a word processor. This is mainly a matter of adding
> features that let you put things in a buffer (and save them in files)
> to get various kinds of formatting effects. To display web pages is an
> even more distant goal; it requires MORE new buffer and display
> features.
>
> I would be very glad to see people start working on some of them.
>
That's if we want to make emacs itself display the web page. I don't see the
point, since other projects do precisely that.
[-- Attachment #2: Type: text/html, Size: 2165 bytes --]
next prev parent reply other threads:[~2008-09-06 10:48 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6fa54e4e0809060348l2ca36872u2445d0824960021b@mail.gmail.com \
--to=smeuuh@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
--cc=lennart.borgman@gmail.com \
--cc=phil@shellarchive.co.uk \
--cc=pmr@pajato.com \
--cc=raman@users.sourceforge.net \
--cc=rms@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.