Groups | Search | Server Info | Login | Register
Groups > gnu.groff.bug > #1998
| From | "G. Branden Robinson" <INVALID.NOREPLY@gnu.org> |
|---|---|
| Newsgroups | gnu.groff.bug |
| Subject | [bug #59030] some warnings [errors] still emitted with -Ww |
| Date | 2020-08-28 05:08 -0400 |
| Message-ID | <mailman.1554.1598605694.2469.bug-groff@gnu.org> (permalink) |
| References | <20200828-034839.sv93119.86587@savannah.gnu.org> <20200828-040209.sv93119.3945@savannah.gnu.org> <20200828-090812.sv108747.14168@savannah.gnu.org> |
Update of bug #59030 (project groff):
Category: None => Core
Status: None => Need Info
Assigned to: None => gbranden
Summary: some warnings still emitted with => some warnings
[errors] still emitted with -Ww
_______________________________________________________
Follow-up Comment #2:
Well, that's 'cause it's an error, not a warning. ;-)
It even says so right there in the diagnostic message, though you'll find
that's a recent innovation; groff 1.22.4 and earlier didn't mention this.
The confusion seen here is exactly why I'm fairly militant about diagnostic
messages always including their diagnostic level.
I am kind of chagrined that my efforts failed here, though.
Anyway, to suppress error messages, you have to use the -E option of groff or
troff.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?59030>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
Back to gnu.groff.bug | Previous | Next | Find similar
[bug #59030] some warnings [errors] still emitted with -Ww "G. Branden Robinson" <INVALID.NOREPLY@gnu.org> - 2020-08-28 05:08 -0400
csiph-web