Re: Possible problem with Gnus

[Richard Stallman <rms@gnu.org>]

    > 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.