Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: Ingo Schwarze Newsgroups: gnu.groff.bug Subject: [bug #59030] some warnings [errors] still emitted with -Ww Date: Sat, 29 Aug 2020 19:32:11 -0400 (EDT) Lines: 50 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> <20200828-111922.sv108747.79157@savannah.gnu.org> <20200828-174503.sv93119.68192@savannah.gnu.org> <20200829-233211.sv97361.91679@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 1598743933 9002 209.51.188.17 (29 Aug 2020 23:32:13 GMT) X-Complaints-To: action@cs.stanford.edu To: "G. Branden Robinson" , Dave , Ingo Schwarze , bug-groff@gnu.org Envelope-to: bug-groff@gnu.org X-PHP-Originating-Script: 1001:sendmail.php X-Savane-Server: savannah.gnu.org:443 [209.51.188.72] X-Savane-Project: groff X-Savane-Tracker: bugs X-Savane-Item-ID: 59030 User-Agent: Mozilla/5.0 (X11; OpenBSD amd64; rv:77.0) Gecko/20100101 Firefox/77.0 X-Apparently-From: 109.42.0.170 (Savane authenticated user schwarze) In-Reply-To: <20200828-174503.sv93119.68192@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: <20200829-233211.sv97361.91679@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> <20200828-050924.sv93119.28373@savannah.gnu.org> <20200828-111922.sv108747.79157@savannah.gnu.org> <20200828-174503.sv93119.68192@savannah.gnu.org> Xref: csiph.com gnu.groff.bug:2014 Follow-up Comment #9, bug #59030 (project groff): gbranden wrote: > I'm fairly militant about diagnostic messages always including their diagnostic level. I like that, and i think it makes a lot of sense in multiple levels. > I'm undecided as to whether it should. I think it is very good that -E implies -Ww. By definition, errors are more severe than warnings, so if the user doesn't even worry about errors, it is eminently logical that they worry about warnings even less. In the unusual situation that somebody isn't interested in errors but wants to see particular warning, they can say something like -E -w break. So there is no missing functionality and no surprising behaviour, unless i misunderstand. > I'm sure there is some resistance to adding another warning category Yes, i for example would appreciate keeping the number of categories small, there are too many already for my taste. I doubt that many users actually used them. Some certainly use -w all and/or -w w but i guess very few bother configuring categories individually. It is generally better to group messages by severity (e.g. error, warning, style issue) than by topic. Easier to use - more likely to actually get used, and used productively. > I'm inclined to leave this open for the time being as just > a documentation bug. I would consider saying "-E implies -W w" (if that is indeed true) at the appropriate place or places reasonable, unless it is already said there. (As an aside, i agree that the warning categories are not just too many but also somewhat ill-designed, but that isn't easy to fix, and even if one were willing to break compat, overhauling a message system tends to require a lot of work, and then there is still a risk that the new system might end up just different and not much better.) _______________________________________________________ Reply to this item at: _______________________________________________ Message sent via Savannah https://savannah.gnu.org/