should enscript set an exit code?

Asked by Eric Bowser

I have a fresh install of 16.04, using enscript 1.6.5.90-2 from apt.

It seems that enscript returns 0 regardless of hitting an error:

spoolprocess@multibox:~$ enscript -o foo "fakefile"
enscript: couldn't open input file "fakefile": No such file or directory
no output generated
spoolprocess@multibox:~$ echo $?
0

Is this expected behavior for this program, an upstream issue, or something Ubuntu specific? This gave me fits trying to troubleshoot a script that processes spool files from a legacy system into PDF files for document management.

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu enscript Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said :
#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.