ghostscript exit status

Article View: gnu.ghostscript.bug

Article #300

Back to gnu.ghostscript.bug Previous Next

#300

From: Karl Berry
Date: Wed, 26 Aug 1992 10:52

9 lines
656 bytes

Ghostscript 2.5 appears not to exit with bad status if an error occurs.
For example:

echo foobar | gs - && echo broken

does indeed print `broken', even though GS correctly reports /foobar is
/undefined.

karl@cs.umb.edu

Technical Details

Message-ID: <199208261852.AA05449@claude.cs.umb.edu>

Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!claude.cs.umb.edu!karl

Show Full Headers

Complete Article Headers

Newsgroups: gnu.ghostscript.bug
Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!claude.cs.umb.edu!karl
From: karl@claude.cs.umb.edu (Karl Berry)
Subject: ghostscript exit status
Message-ID: <199208261852.AA05449@claude.cs.umb.edu>
Sender: gnulists@ai.mit.edu
Reply-To: karl@cs.umb.edu
Organization: GNUs Not Usenet
Distribution: gnu
Date: Wed, 26 Aug 1992 10:52:33 GMT
Approved: bug-ghostscript@prep.ai.mit.edu
Lines: 10