On Sunday 07 February 2010 01:46:42 am Werner LEMBERG wrote:
Of course! I would be really glad if there are helping hands since my
time is quite limited (and I'm a lazy person).
Werner, if you're lazy, the rest of us might as well retire our
shingles and sink back into the slough of entropy.
I'm seeing these warnings in tables that *aren't* breaking the right
margin as well as ones that are.
Hmm. Perhaps the overshoot is very small, thus not visible to the
eye? Perhaps I can add some user-controlled fuzziness (similar to
TeX). If you don't think this is the cause please send me
warning: around line 35: table wider than line width
warning: around line 35: table squeezed horizontally to fit line length
warning: around line 367: table wider than line width
warning: around line 367: column separation set to zero
I've included a patch to include the file name in the
Werner LEMBERG wrote:
I'm seeing these warnings in tables that *aren't* breaking the right
margin as well as ones that are.
Hmm. Perhaps the overshoot is very small, thus not visible to the
eye? Perhaps I can add some user-controlled fuzziness (similar to
TeX). If you don't think
I'm seeing these warnings in tables that *aren't* breaking
the right margin as well as ones that are.
Hmm. Perhaps the overshoot is very small, thus not visible
to the eye? Perhaps I can add some user-controlled
fuzziness (similar to TeX). If you don't think this is the
cause
Hmm. Perhaps the overshoot is very small, thus not visible
to the eye? Perhaps I can add some user-controlled
fuzziness (similar to TeX). If you don't think this is the
cause please send me such an offending table for further
inspection.
That's pretty likely, the overshoot is not
I'm seeing these warnings in tables that *aren't* breaking
the right margin as well as ones that are.
Hmm. Perhaps the overshoot is very small, thus not visible
to the eye?
That's pretty likely, the overshoot is not easily noticed.
There appear to be two different kinds of warnings:
I
I would support making tbl warnings optional, to be in line with
troff, and other reasons, for example if a table is deliberately
wider than the line width.
Then you should increase the line width temporarily.
Werner
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
I'm now seeing warnings like this when I runoff a manual containing tbl tables
that use the expand global option:
./Installation.ms:3: warning: numeric expression expected (got `i')
warning: around line 35: table wider than line width
warning: around line 35: table squeezed horizontally to fit
I would support making tbl warnings optional,
to be in line with troff, and other reasons,
for example if a table is deliberately wider
than the line width. A new flag -w to enable
warnings?
Denis
Denis M. Wilson wrote:
I would support making tbl warnings optional,
to be in line with troff, and other reasons,
for example if a table is deliberately wider
than the line width. A new flag -w to enable
warnings?
I was thinking maybe a global option like nowarn -- the warnings are
12 matches
Mail list logo
