From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Postcript
Date: Sun, 11 May 2003 23:40:16 -0400 [thread overview]
Message-ID: <e414cc8beaeaf65f4026bbd3345902f7@plan9.bell-labs.com> (raw)
In-Reply-To: <20030512023246.3702.qmail@g.bio.cse.psu.edu>
> | >The real problem is what gets printed before, namely
> | >that Ghostscript has produced unexpected output.
>
> Postscript previewers really shouldn't croak when that happens, though.
> gv just reports that stuff to the user.
True enough, but page currently can't tell interpreter
errors apart from postscript's standard output. Usually
output is the interpreter barfing on bad postscript.
Maybe there's some way to silence the prints.
next prev parent reply other threads:[~2003-05-12 3:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-11 15:35 northern snowfall
2003-05-11 15:43 ` northern snowfall
2003-05-11 18:26 ` Joel Salomon
2003-05-11 18:37 ` Joel Salomon
2003-05-12 0:05 ` Russ Cox
2003-05-12 2:59 ` northern snowfall
2003-05-12 2:32 ` Scott Schwartz
2003-05-12 3:40 ` Russ Cox [this message]
2003-05-12 3:41 ` northern snowfall
2003-05-12 8:56 ` Douglas A. Gwyn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e414cc8beaeaf65f4026bbd3345902f7@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).