[bug #61379] [tmac] report failure to run tbl when its macros are used

[G. Branden Robinson]

Update of bug #61379 (project groff):

                Category:               Macro man => Macro - others/general 
                  Status:               Need Info => None                   
                 Summary: [tmac] Detect use of preprocessor "tbl" and "table
wider than line" => [tmac] report failure to run tbl when its macros are used

    _______________________________________________________

Follow-up Comment #5:

[comment #3 comment #3:]
>   The subject "Detect ... "table wider than line" is
>   misleading.
> 
>   "tbl" already reports that, but gives no information about
>   the line length and width of the table.

tbl(1) is a preprocessor.  That means that when it runs, the
document has not been formatted.  The output device's _DESC_
file has not been read, therefore the line length is not known
to it.

tbl cannot report this information when it runs; it can, at
best, generate groff code to produce it, as cited in comment #4.

However, at the time _those_ diagnostics are emitted, the
table's _own_ width is not yet known; the `TW` register is not
defined until the table region ends.

So the only ways to get both pieces of information out are to
(1) have multiple diagnostics or (2) suppress diagnostics from
tbl (with the "nowarn" option) and have the macro package's `TE`
macro emit both data in one message.

I don't support having man(7) issue an _additional_ diagnostic
on top of the one tbl(1) already emits when a table row is too
wide.  Since bug #61854 is now fixed, we can be confident that
that is the case.

Option (2) is also unacceptable because we can't just tell
people to rewrite all their table regions to include "nowarn";
further, that would suppress legitimate diagnostics.  Having
"nowarn" be the default would be even worse.

On top of the aforementioned bug being fixed, bug #60598 is as
well.  This means that when tbl's generated groff diagnostics
complain, they do so about the correct line number.

This seems entirely adequate to me.  We tell the people when
their table row is overrunning, and we tell them what line of
source input to look at to resolve the issue.

The scope of this bug should be limited to adding `TW`-checking
diagnostics to other macro packages' `TE` macros.

The rest of it, I consider invalid.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61379>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/