Werner LEMBERG wrote:
I was thinking maybe a global option like "nowarn" -- the warnings
are generally useful, but once a particular table has been debugged
you wouldn't want to hear from it again.
This should be quite easy to implement, and I would include it into
groff if someone (you?) is writing it, but, as mentioned in another
mail, I don't see much use to that, given that better, less hacky
solutions are available.
Like I said, I'm seeing these warnings in tables that *aren't*
breaking the right margin as well as ones that are. It seems like
combining the global option "expand" with a column width specifier is
a good (but not 100% reliable) way to trip the warnings. In many
other cases, the margin break is either so miniscule as to be
unnoticed, or is an acceptable tradeoff to solve bigger problems.
I already redirect stderr, but it would be nice to reduce the amount
of noise in that file so I can more easily find real problems. You're
right about how easy it was to implement; I'll test it tomorrow &
submit the patch if it seems to do the right thing.
-- Larry
