From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Possible problem with Gnus Date: Fri, 14 May 2004 17:01:57 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <20040509230720.GB20485@fencepost> Reply-To: rms@gnu.org NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1084572806 31601 80.91.224.253 (14 May 2004 22:13:26 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 14 May 2004 22:13:26 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sat May 15 00:13:15 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 1BOkvb-00011x-00 for ; Sat, 15 May 2004 00:13:15 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BOkvb-00019P-00 for ; Sat, 15 May 2004 00:13:15 +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 1BOklC-0004lr-Vb for emacs-devel@quimby.gnus.org; Fri, 14 May 2004 18:02:31 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BOkl7-0004lb-AO for emacs-devel@gnu.org; Fri, 14 May 2004 18:02:25 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BOkkb-0004h5-2m for emacs-devel@gnu.org; Fri, 14 May 2004 18:02:24 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BOjoc-0004hL-8F for emacs-devel@gnu.org; Fri, 14 May 2004 17:01:58 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1BOjob-00070z-IZ; Fri, 14 May 2004 17:01:57 -0400 Original-To: David Kastrup In-reply-to: (message from David Kastrup on 13 May 2004 19:25:44 +0200) 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:23435 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:23435 > If there are bugs in the Postscript support, please start reporting > them one by one. This is a feature that is supposed to work, > and if it doesn't, we should fix it. It is not a feature that is supposed to work. From the code in lisp/gs.el: This makes it somewhat less urgent. But we still want this feature to work. We should start fixing the problems in it, even if we do so one by one. To set an example, I will add -dSAFER to gs-options. The only platform on which the postscript device works in the first place is X11. That platform is more important than all the rest. While we do support Windows and MacOS, they should never weigh more in our decisionmaking than the GNU operating system. 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? 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.