Follow-up Comment #2, bug #53043 (project groff): To me, these conclusions are based on speculations and imagination.
Decisions are made here (and other places) for others, without knowing what they would like more and why. Suppressing warnings is the duty (and responsibility) of the user of a software not the writer's. The software writer should provide (unconditionally) all diagnostics that can improve the quality of the input and output. One of the fundamental obligations of programs is to test the input for validity; or proof me wrong. Every user can filter warnings from the output, but can't add nonexisting ones without changing the issuing program. "man-db" even by default removes all warnings, making maintainers unaware of them. So actually it deceives them. Any software writer with a professional attitude tells users if something in the input is not correct (not optimal), on the condition, that he knows about it and knows how to report it to the user. (Or how is professional attitude defined?) (What about ethical issues?) Why not report ".BR XY"? Maybe ".BR X Y" is meant! Is ".BR XY" the correct use of the macro? Does ".BI XY" mean "BoldItalic"? Has it an obvious semantics (meaning)? If yes, what is it to everybody? Example in "man.1": .BR dvips. So, what does more harm nowadays 1) issuing more warnings by default or unconditionally? (until fixed!) 2) avoiding warnings by default or altogether? (Keep wrongdoings forever(?); engage in time theft!) Nowadays maintainers are stealing time from others, as they do not themselves fix things, that are or could be reported by using (supporting) the full (proposed) potential (capability) of the software they use. ### "This second radical novelty shares the usual fate of all radical novelties: it is denied, because its truth would be too discomforting. I have no idea what this specific denial and disbelief costs the United States, but a million dollars a day seems a modest guess." P. xxix in: On the Cruelty of Really Teaching Computing Science Edsger W. Dykstra (Dijkstra) SIGCSE Bulletin 1989, 21(1), pp. xxv-xxxix. Also "www.cs.utexas.edu/users/EWD/" # "Since breaking out of bad habits, rather than acquiring new ones, is the toughest part of learning we must expect from that system permanent mental damage for most students exposed to it." P. xxxvii in: On the Cruelty of Really Teaching Computing Science Edsger W. Dykstra (Dijkstra) SIGCSE Bulletin 1989, 21(1), pp. xxv-xxxix. Also "www.cs.utexas.edu/users/EWD/" # "The problems of the real world are primarily those you are left with when you refuse to apply their effective solutions." P. xxxviii in: On the Cruelty of Really Teaching Computing Science Edsger W. Dykstra (Dijkstra) SIGCSE Bulletin 1989, 21(1), pp. xxv-xxxix. Also "www.cs.utexas.edu/users/EWD/" _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?53043> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/ _______________________________________________ bug-groff mailing list firstname.lastname@example.org https://lists.gnu.org/mailman/listinfo/bug-groff