Groups | Search | Server Info | Login | Register

Groups > gnu.groff.bug > #2002

[bug #59030] some warnings [errors] still emitted with -Ww

Show all headers | View raw

Follow-up Comment #6, bug #59030 (project groff):

[comment #3 comment #3:]
> Also, it appears that -E implies -Ww.
> 
> I'm undecided as to whether it should. 

Yeah, I can see arguments either way, though if it continues to work this way,
this should be documented.

[comment #4 comment #4:]
> errors and warnings are simply different things the program can yell about.

I do wonder whether this particular problem really rises to the level of
"error": it's nonfatal and about as severe as some other things deemed
warnings.  For the very particular use case mentioned in comment #1, it would
be nice to be able to turn that message off with an appropriate .warn request,
and then turn it back on again after the attempt to set .g; there appears to
be no equivalent in-document mechanism for emulating -E.

But overall I'd say this is working as designed, so probably this report
should be closed.

    _______________________________________________________

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

Thread

[bug #59030] some warnings [errors] still emitted with -Ww Dave <INVALID.NOREPLY@gnu.org> - 2020-08-28 06:09 -0400

csiph-web