Follow-up Comment #19, bug #65474 (group groff):
[comment #18 comment #18:]
> I propose to fix this by killing the warning category along with
> the spuriousness.
With two longtime groff users (Tadziu and Bjarni, with me still on the fence)
arguing that the warning isn't spurious, I wonder if this proposal should be
put before a wider audience.
I think clearly documenting the situation described in bug #59434 would
greatly simplify explaining to users why this warning occurs and how to code
for groff's nonintuitive flow control.
If there are incompatibilities between how groff handles .if/.ie/.el and how
ancestral and peer troffs do, those should also be fixed or documented before
axing arguably valid warnings.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65474>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
