gbranden pushed a commit to branch master
in repository groff.
commit 469ce753dd001abba29f443fcd2715177732524f
Author: G. Branden Robinson <[email protected]>
AuthorDate: Wed Apr 29 11:39:17 2026 -0500
doc/groff.texi.in: Fix style nits.
* Favor footnotes over inlining for forward references.
* Break input lines in a places convenient for roffing and diffing.
---
doc/groff.texi.in | 23 ++++++++++++++---------
1 file changed, 14 insertions(+), 9 deletions(-)
diff --git a/doc/groff.texi.in b/doc/groff.texi.in
index 91936bd90..115b95b43 100644
--- a/doc/groff.texi.in
+++ b/doc/groff.texi.in
@@ -12053,15 +12053,20 @@ flushing out the pending output line in the usual way.
@cindex interrupted line register (@code{.int})
@cindex continued output line register (@code{.int})
-The @code{.int} register interpolates a positive value only if the
-pending output line has been continued with @code{\c}; this datum is
-associated with the environment
-(@pxref{Environments}).@footnote{Historically, the @code{\c} escape
-sequence has proven challenging to characterize. Some sources say it
-``connects the next input text'' (to the input line on which it
-appears); others describe it as ``interrupting'' text, on the grounds
-that a text line is interrupted without breaking, perhaps to inject a
-request invocation or macro call.}
+The @code{.int} register interpolates a positive value
+only if the pending output line has been continued with
+@code{\c};
+this datum is associated
+with the environment.@footnote{@xref{Environments}.
+Historically,
+the
+@code{\c}
+escape sequence has proven challenging to characterize.
+Some sources say it ``connects the next input text''
+(to the input line on which it appears);
+others describe it as ``interrupting'' text,
+on the grounds that a text line is interrupted without breaking,
+perhaps to inject a request invocation or macro call.}
@endDefesc
_______________________________________________
groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit
