[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #62559] [gt]roff -E: say "warnings" instead of "errors"

From: G. Branden Robinson
Subject: [bug #62559] [gt]roff -E: say "warnings" instead of "errors"
Date: Wed, 1 Jun 2022 20:37:27 -0400 (EDT)

Update of bug #62559 (project groff):

                  Status:                    None => Need Info              
             Assigned to:                    None => gbranden               


Follow-up Comment #1:

[comment #0 original submission:]
> Subject: [gt]roff -E: say "warnings" instead of "errors"
>   Real errors should not be suppressed and "*roff" has only categories
> of warnings.

I don't understand this report.  GNU troff has plenty of error messages.

$ test -z "$(printf '\\' | groff 2>&1)" && echo empty input
$ test -z "$(printf '\\' | groff -E 2>&1)" && echo empty input
empty input

That's groff 1.22.4.  groff Git HEAD prefixes such messages with "error:".

>   The man pages (groff.1.man, troff.1.man) say:
> .B \-E
> Inhibit
> .I @g@troff
> error messages;
> implies
> .BR \-Ww .

Yes, that sounds correct to me.


Reply to this item at:


Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]