Follow-up Comment #16, bug #67612 (group groff): On Thursday, 30 October 2025 08:43:20 GMT G. Branden Robinson wrote: > Follow-up Comment #15, bug #67612 (group groff): > > > [comment #14 comment #14:] > >> Thanks, Deri, this fully explains the results I'm seeing. > > What needs to be done to resolve this ticket?
I have a pending change to "downgrade" the two messages Dave identifies as not
really warnings to "Notices", since they are informational rather than
reporting a problem with the produced pdf, and so will not cause a non-zero
exit.
> Improve the documentation?
>
> Add a command-line option or environment variable to support this "treat
> warnings as errors" behavior, and change the default to not do so?
The change in behaviour (setting an exit code on warnings) was added so that
make would abort if gropdf reported a warning, at Branden's suggestion. I
don't mind if the behaviour is selectable in some way, but I think after the
"downgrading" only messages which denote possible problems with the produced
pdf will result in non-zero exit status. Also, this only affects situations
where groff is used in a workflow where the exit status is checked, which is a
subset of usual uses of groff - to produce a single document from the command
line.
> Both? Something else?
>
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67612>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
