Update of bug #63011 (project groff):
Summary: troff/input.cpp: wrong(?) warning from
"do_overstrike" => troff/input.cpp: wrong warning from "do_overstrike"
_______________________________________________________
Follow-up Comment #1:
Interesting, I don't see any fundamental behavior difference between 1.22.4
and git HEAD here. In both I get the warning only if warnings are enabled;
the only difference is that 1.22.4 emits a terser version:
$ printf '\o\no+\nOne.\n' | groff -ww | wc
troff: <standard input>:2: warning: missing closing delimiter
236 630 5730
* If the documentation is correct, there should be no warning.
* If the documentation is incorrect, and newline is not a valid \o delimiter,
the warning should not complain only about its closing delimiter.
* If the documentation is correct, but based on it recommending against this
practice, a warning is emitted, the warning should tell the user "that's a bad
idea" rather than "something's missing."
So no matter the situation, the current warning is inaccurate. Updating
Summary accordingly.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?63011>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
