Follow-up Comment #3, bug #67612 (group groff): The man page text I quoted in comment #1 has been clarified since that commit. For context, the current text of the whole section is:
Exit status
0 gropdf successfully produced a PDF document.
1 gropdf experienced a critical error, or could not interpret its
arguments. No PDF was produced, or the document produced will be
unusable.
2 gropdf emitted warnings. The document produced may be usable,
but
may fail to render as desired.
Based on this, I think my conclusion still holds: If something may make a
document fail to render as desired, this can reasonably be considered an
error, not a warning (but also not a critical error, as defined in the item
above).
From code inspection, it looks like the sorts of things that trigger this are
the user asking for an unrecognized paper size, an unsupported PDF version, or
a nonexistent image file. Those all fall under "may fail to render as
desired," so I don't have a quarrel with considering them errors, and exiting
with a nonzero code.
But "You would see a noticeable speedup" falls under the description
"successfully produced a PDF document" above, so should exit with 0. That is,
in the parlance of gropdf.pl, this should be a Notice rather than a Warn.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67612>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
