[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[groff] 30/49: doc/groff.texi: Fix correctness and style nits.
From: |
G. Branden Robinson |
Subject: |
[groff] 30/49: doc/groff.texi: Fix correctness and style nits. |
Date: |
Sun, 25 Sep 2022 17:02:58 -0400 (EDT) |
gbranden pushed a commit to branch master
in repository groff.
commit a9c00a58e08fd228fc238a8a93d6c373cb905b0b
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Fri Sep 23 12:39:59 2022 -0500
doc/groff.texi: Fix correctness and style nits.
* Not all escape sequences interpreted in copy mode perform
interpolations. \" and \# are exceptions, for instance.
* It is macro _calls_ that can recurse, not really macros themselves.
---
doc/groff.texi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/groff.texi b/doc/groff.texi
index e71b40467..ebf30d6a4 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -5309,9 +5309,9 @@ perhaps less obviously, we could also have defined them
@emph{after}
the body of a macro definition is not (completely) interpreted, but
stored instead (@pxref{Copy Mode}). While a macro is being defined (or
appended to), requests are not interpreted and macros not interpolated,
-whereas some commonly used escape sequences @emph{are} interpolated.
-@code{roff} systems also support recursive macros---as long as you have
-a way to break the recursion (@pxref{Conditionals and Loops}).
+whereas some commonly used escape sequences @emph{are} interpreted.
+@code{roff} systems also support recursive macro calls, as long as you
+have a way to break the recursion (@pxref{Conditionals and Loops}).
Maintainable @code{roff} documents tend to arrange macro definitions to
minimize forward references.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [groff] 30/49: doc/groff.texi: Fix correctness and style nits.,
G. Branden Robinson <=