doc/groff.texi.in: Tweak "Debugging" section.

* Recast; challenging debuggability is not a unique property of GNU
  troff, and in fact it's easier with our *roff than any other.  Who
  else empowers you to dump the abstract syntax tree of the document?
* Locate synchroniztion comment bumper more precisely.
This commit is contained in:
G. Branden Robinson 2026-01-15 17:37:55 -06:00
parent 633e4123a9
commit a18efe6280

View File

@ -20335,7 +20335,6 @@ restore tokens are removed.
@c =====================================================================
@need 1000
@c BEGIN Keep parallel with section "Debugging" of groff(7).
@node Debugging, Implementation Differences, GNU @command{troff} Internals, GNU troff Reference
@section Debugging
@cindex debugging
@ -20347,15 +20346,17 @@ front of it until it works and if you still have problems add a \c.}
@c https://www.tuhs.org/pipermail/tuhs/2021-February/023137.html
@end flushright
GNU
@command{troff} @c GNU
is not the easiest language to debug,
The
@code{roff}
language family
is not the easiest to debug,
in part thanks to its design features
of recursive interpolation
and the use of multi-stage pipeline processing
in the surrounding system.
Nevertheless there exist several features useful for troubleshooting.
@c BEGIN Keep parallel with section "Debugging" of groff(7).
Preprocessors use the @code{lf} request to preserve the identity of the
line numbers and names of input files.
GNU