Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: Dave Newsgroups: gnu.groff.bug Subject: [bug #59030] some warnings [errors] still emitted with -Ww Date: Fri, 28 Aug 2020 06:09:24 -0400 (EDT) Lines: 34 Approved: bug-groff@gnu.org Message-ID: References: <20200828-034839.sv93119.86587@savannah.gnu.org> <20200828-040209.sv93119.3945@savannah.gnu.org> <20200828-090812.sv108747.14168@savannah.gnu.org> <20200828-091501.sv108747.67103@savannah.gnu.org> <20200828-091824.sv108747.87153@savannah.gnu.org> <20200828-044712.sv93119.69592@savannah.gnu.org> <20200828-050924.sv93119.28373@savannah.gnu.org> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain;charset=UTF-8 X-Trace: usenet.stanford.edu 1598609366 26732 209.51.188.17 (28 Aug 2020 10:09:26 GMT) X-Complaints-To: action@cs.stanford.edu To: "G. Branden Robinson" , Dave , bug-groff@gnu.org Envelope-to: bug-groff@gnu.org X-PHP-Originating-Script: 1001:sendmail.php X-Savane-Server: savannah.gnu.org:443 [2001:470:142::72] X-Savane-Project: groff X-Savane-Tracker: bugs X-Savane-Item-ID: 59030 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Firefox/45.0 X-Apparently-From: 2605:a601:ab42:5b00:d79a:70a3:b6a4:34bf (Savane authenticated user barx) In-Reply-To: <20200828-044712.sv93119.69592@savannah.gnu.org> X-BeenThere: bug-groff@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Bug reports for the GNU version of nroff, troff et al" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: <20200828-050924.sv93119.28373@savannah.gnu.org> X-Mailman-Original-References: <20200828-034839.sv93119.86587@savannah.gnu.org> <20200828-040209.sv93119.3945@savannah.gnu.org> <20200828-090812.sv108747.14168@savannah.gnu.org> <20200828-091501.sv108747.67103@savannah.gnu.org> <20200828-091824.sv108747.87153@savannah.gnu.org> <20200828-044712.sv93119.69592@savannah.gnu.org> Xref: csiph.com gnu.groff.bug:2002 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: _______________________________________________ Message sent via Savannah https://savannah.gnu.org/