From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Andy Tai Newsgroups: gmane.emacs.devel Subject: Re: Possible problem with Gnus Date: Sat, 22 May 2004 20:48:56 -0700 (PDT) Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <20040523034856.3966.qmail@web50901.mail.yahoo.com> References: Reply-To: atai@atai.org NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1085295812 17829 80.91.224.253 (23 May 2004 07:03:32 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 23 May 2004 07:03:32 +0000 (UTC) Cc: Andy Tai , monnier@iro.umontreal.ca, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sun May 23 09:03:21 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BRn0z-0002wd-00 for ; Sun, 23 May 2004 09:03:21 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BRn0y-00078c-00 for ; Sun, 23 May 2004 09:03:21 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BRlfp-0001sU-1W for emacs-devel@quimby.gnus.org; Sun, 23 May 2004 01:37:25 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BRlej-0001hm-Fa for emacs-devel@gnu.org; Sun, 23 May 2004 01:36:17 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BRle6-0001YA-3V for emacs-devel@gnu.org; Sun, 23 May 2004 01:36:11 -0400 Original-Received: from [206.190.38.121] (helo=web50901.mail.yahoo.com) by monty-python.gnu.org with smtp (Exim 4.34) id 1BRle5-0001Y2-MJ for emacs-devel@gnu.org; Sun, 23 May 2004 01:35:37 -0400 Original-Received: from [210.21.224.54] by web50901.mail.yahoo.com via HTTP; Sat, 22 May 2004 20:48:56 PDT X-RocketYMMF: lichengtai Original-To: rms@gnu.org, David Kastrup In-Reply-To: X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:23843 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:23843 Hi, sorry the previous mail was sent prematurely. I meant I can look into implementing this interface, but I cannot promise at a time frame right now. Andy --- Richard Stallman wrote: > Andy, we have been talking about problems in Emacs > code > to display postscript in the middle of a document. > > > The sane thing to do is to serialize the > whole GhostScript > > operation to have at most one GhostScript > process running, and > > to not restart this process as long as > images remain to be > > rendered. > > > > That does sound desirable. However, > > > > For this to work, one has to stop > passing the information > > through an XPixMap but has to go through a > file or pipe. > > > > Using a pixmap is preferable, in general. Why > do you think > > using a single Ghostscript process is > incompatible with using > > a pixmap? > > Because the interface to GhostScript that is > used for passing the > XPixMap Id and the respective sizes is queried > just at the start of > GhostScript. > > I think the solution for this is to make a new > interface > to allow Emacs to specify the pixmap to an existing > GhostScript > process when reusing it for another image. > > Andy, can you implement such an interface for Emacs > to use? > > > In contrast, preview-latex first deals > with on-screen images. > > Once they are dealt with, it reverts to > rendering the rest > > off-screen. > > > > That would be a good optimization to add. > > Rendering off-screen material is actually not as > much an optimization, > but an interactivity feature. It means that > once GhostScript is > through, scrolling through the file is not > computationally expensive. > > However, if some document has thousands of > images, it would be saner > to render them just to disk in case you'll need > them, but not burden > Emacs' memory with them unless one actually > moves there. > > That makes sense. Can that be done easily with > reuse of a > single GhostScript process, with the existing > GhostScript features? > If not, what new feature do we need?