From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Richard M. Stallman" Newsgroups: gmane.emacs.devel Subject: Re: An Emacs plug-in for a browser (Firefox?) Date: Tue, 09 Sep 2008 04:11:37 -0400 Message-ID: References: <48C0FC53.4020806@gmail.com> <6fa54e4e0809050420i5132ace5red5a011b69ecd1ed@mail.gmail.com> <8763p795cq.fsf@cyd.mit.edu> <87iqt6q0na.fsf@cyd.mit.edu> <6fa54e4e0809081007l68f1df2ei71450cf3483f2d17@mail.gmail.com> <48C5778F.2020203@emf.net> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: ger.gmane.org 1220948180 4164 80.91.229.12 (9 Sep 2008 08:16:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 9 Sep 2008 08:16:20 +0000 (UTC) Cc: pmr@pajato.com, cyd@stupidchicken.com, lennart.borgman@gmail.com, joakim@verona.se, emacs-devel@gnu.org, smeuuh@gmail.com, raman@users.sourceforge.net, phil@shellarchive.co.uk, monnier@iro.umontreal.ca To: Thomas Lord Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Sep 09 10:17:12 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 1KcyPL-00021M-7S for ged-emacs-devel@m.gmane.org; Tue, 09 Sep 2008 10:17:07 +0200 Original-Received: from localhost ([127.0.0.1]:57067 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KcyOK-0007f4-Jf for ged-emacs-devel@m.gmane.org; Tue, 09 Sep 2008 04:16:04 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KcyLr-0006KX-Ca for emacs-devel@gnu.org; Tue, 09 Sep 2008 04:13:31 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KcyLn-0006JT-5E for emacs-devel@gnu.org; Tue, 09 Sep 2008 04:13:28 -0400 Original-Received: from [199.232.76.173] (port=38510 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KcyLk-0006Is-NE for emacs-devel@gnu.org; Tue, 09 Sep 2008 04:13:25 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]:38743) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KcyLk-0006w2-Er for emacs-devel@gnu.org; Tue, 09 Sep 2008 04:13:24 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.67) (envelope-from ) id 1KcyK1-00031q-42; Tue, 09 Sep 2008 04:11:37 -0400 In-reply-to: <48C5778F.2020203@emf.net> (message from Thomas Lord on Mon, 08 Sep 2008 12:05:51 -0700) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:103725 Archived-At: Emacs has the concept that two windows can look at the same buffer. Displaying a buffer containing an XEmbed in two Emacs windows ought to work work -- perhaps only because it would not mean what one might expect. Suppose you put an XEmbed widget into an Emacs buffer (perhaps with a special kind of `display' property on part of the text) and display the buffer in a window. As with any other thing in the Emacs buffer, Emacs has to know how tall it should appear. You would have to specify this, in the `display' property I suppose. Then when Emacs displays that buffer in the window, it will show part of the XEmbed if appropriate, just as it might show all or part of an image in the buffer. It should not be hard for Emacs to do this in two windows in parallel, if it can make the other program display into a pixmap of the specified size. Note that scrolling an Emacs window will not tell the other program anything. It will just tell Emacs to display a different part of the appearance of the buffer in that window. I think that people have a different behavior in mind for the browser: namely to hand over a particular Emacs window to the browser and expecting it to use the whole of that window, knowing the size of that window. That would be a different kind of feature. Instead of having an XEmbed widget in the text in a buffer, it would mean having a buffer that is simply an alias for displaying the output of another program. So if you tell an Emacs window to display that buffer, it really means to telling the other program to use and control that Emacs window. It would be hard to do that in more than one window, unless the other program supports multiple windows. If it does, it ought to be able to handle two Emacs windows in parallel the same way it would handle two other windows in parallel. Most graphical browsers seem to be able to do this. Another way to handle doing this in two windows at once is to run two copies of the program in parallel. That might be ok for some simple programs.