Follow-up Comment #8, bug #67612 (group groff): [comment #7 comment #7:] > Is use of exit status 4 necessary? Is _gropdf_ already using > status 3 for something?
The exit status is coming from groff, not gropdf; I presume groff is munging
it in some manner as the documentation you quoted implies, although the
specific munging does not seem to be exactly in line with that snippet, unless
one reads "setting bit 2 if a command exited with a failure status" as also
implying "and clearing whatever bits the failing command returned on exit."
Lacking a test-gropdf analogue to the test-groff script, running the latest
gropdf directly is not straightforward.
$ echo 'Yo!' | $HOME/groff/build/test-groff -Z -Tpdf |
$HOME/groff/build/gropdf
gropdf: fatal error: failed to open 'download' file
There's probably a way to make it work, but it's not worth my time to figure
out, since all I care about is "is it 0 or not-0?"
> Conventionally, in _groff_, we assign exit statuses of low
> value meanings in alignment with common practice.
>
> 0: success
> 1: false; expected failure; unable to perform desired operation
> 2: usage error
That is in line with the documented gropdf exit values quoted in comment #3.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67612>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
