From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Antoine Levitt" Newsgroups: gmane.emacs.devel Subject: Re: An Emacs plug-in for a browser (Firefox?) Date: Sat, 6 Sep 2008 12:48:09 +0200 Message-ID: <6fa54e4e0809060348l2ca36872u2445d0824960021b@mail.gmail.com> References: <18624.40059.414121.633475@gargle.gargle.HOWL> <48C0BB3A.4080201@pajato.com> <87zlmnezy9.fsf@shellarchive.co.uk> <48C0FC53.4020806@gmail.com> <6fa54e4e0809050420i5132ace5red5a011b69ecd1ed@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_72944_15496408.1220698089122" X-Trace: ger.gmane.org 1220698197 13961 80.91.229.12 (6 Sep 2008 10:49:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 6 Sep 2008 10:49:57 +0000 (UTC) Cc: pmr@pajato.com, lennart.borgman@gmail.com, joakim@verona.se, emacs-devel@gnu.org, raman@users.sourceforge.net, phil@shellarchive.co.uk To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Sep 06 12:50:51 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KbvNS-0000Jr-VZ for ged-emacs-devel@m.gmane.org; Sat, 06 Sep 2008 12:50:51 +0200 Original-Received: from localhost ([127.0.0.1]:33702 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KbvMT-0001AP-Cx for ged-emacs-devel@m.gmane.org; Sat, 06 Sep 2008 06:49:49 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KbvKx-0000cu-DU for emacs-devel@gnu.org; Sat, 06 Sep 2008 06:48:15 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KbvKu-0000bv-Qe for emacs-devel@gnu.org; Sat, 06 Sep 2008 06:48:14 -0400 Original-Received: from [199.232.76.173] (port=41088 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KbvKt-0000bd-5A for emacs-devel@gnu.org; Sat, 06 Sep 2008 06:48:11 -0400 Original-Received: from ey-out-1920.google.com ([74.125.78.146]:27227) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KbvKs-0000MD-M8 for emacs-devel@gnu.org; Sat, 06 Sep 2008 06:48:11 -0400 Original-Received: by ey-out-1920.google.com with SMTP id 4so369039eyg.24 for ; Sat, 06 Sep 2008 03:48:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=FZfiOWvK7rbeXTEzvKRjwoVGInQrpjwgEomiAftEnB0=; b=WZhYVgPxQvyYWBXKCxOvAfCIjisWcm2bpiEmR0kgR8C2ASQpKwMeaVm25PTqg3APEJ 7wRy6G2E4ayqi1XK37XZAibumR3yXNDnH3eZM8++EbNEAbkA0ouVduwp6995iFw8TNXH VBj0vJTc4JL7kxe32qt7NIL+7HR4ME3zTBVOA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=cR3gAO47BpZNU2t5hC7cuiECamq2SvmEQJHH1H4eZOQSills9k28kskJI8QUD1SxYX TxQl40VEEABArW34EcEwRFyTbND7CDomjHna/nNOWlz/CSzg7NdYzuqdiNdFiOyzc6UX 9f1jqFGlGNAQ2emNhqunDmE0r8w4iPEU1NMUw= Original-Received: by 10.210.25.19 with SMTP id 19mr6246887eby.113.1220698089134; Sat, 06 Sep 2008 03:48:09 -0700 (PDT) Original-Received: by 10.210.141.18 with HTTP; Sat, 6 Sep 2008 03:48:09 -0700 (PDT) In-Reply-To: X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:103585 Archived-At: ------=_Part_72944_15496408.1220698089122 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 2008/9/6 Richard M. Stallman > 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. ------=_Part_72944_15496408.1220698089122 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline


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.

------=_Part_72944_15496408.1220698089122--