gbranden pushed a commit to branch master
in repository groff.
commit de824170f0c9e27d05c2444f348beff47a771a6a
Author: G. Branden Robinson <[email protected]>
AuthorDate: Sat Jan 10 20:01:15 2026 -0600
doc/groff.texi.in: Tweak "Punning Names" section.
* Use "recall" and non-parenthetical phrase for backward references.
* Apply poor man's keep.
* Break input lines in a roff-friendly way.
---
doc/groff.texi.in | 22 +++++++++++++++-------
1 file changed, 15 insertions(+), 7 deletions(-)
diff --git a/doc/groff.texi.in b/doc/groff.texi.in
index 026fd5a50..f55ed67f3 100644
--- a/doc/groff.texi.in
+++ b/doc/groff.texi.in
@@ -18744,12 +18744,13 @@ Truly.
@noindent
By ending each text line of the macros with an escaped
@key{RET},
-we get the desired effect
-(recall @pxref{Line Continuation}).@footnote{We must
+we get the desired effect;
+recall @ref{Line Continuation}.@footnote{We must
double the backslash.
Recall @ref{Copy Mode}.}
What would have happened if we had used only one backslash in each case?
+@need 1000
Interpolating a string does not hide existing macro arguments. We can
also place the escaped newline outside the string interpolation instead
of within the string definition. Thus, in a macro, a more efficient way
@@ -18767,8 +18768,10 @@ is
@endExample
@noindent
-The latter calling syntax doesn't change the value of @code{\$0}, which
-is then inherited from the calling macro (@pxref{Parameters}).
+The latter calling syntax doesn't change the value of
+@code{\$0},
+which is then inherited from the calling macro;
+recall @ref{Parameters}.
It is sometimes convenient to copy a single-line diversion to a string,
which can then be interpolated with @code{\*}.
@@ -18787,9 +18790,14 @@ interpolation system
@endExample
@noindent
-In the foregoing, we see that formatted output can thus be stored in a
-string. The @code{\c} escape sequence prevents the subsequent newline
-from being interpreted as a break (again, @pxref{Line Continuation}).
+In the foregoing,
+we see that formatted output can thus be stored in a string.
+The
+@code{\c}
+escape sequence prevents the subsequent newline
+from being interpreted as a break;
+again,
+recall @ref{Line Continuation}.
Copying multi-output line diversions produces unexpected results.
_______________________________________________
groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit
