[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[groff] 10/17: doc/groff.texi (Conditional Blocks): Clarify.
From: |
G. Branden Robinson |
Subject: |
[groff] 10/17: doc/groff.texi (Conditional Blocks): Clarify. |
Date: |
Fri, 25 Jun 2021 18:05:18 -0400 (EDT) |
gbranden pushed a commit to branch master
in repository groff.
commit a6d8eec045a99e45e7b53d1200305bddf513d15c
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Fri Jun 25 09:30:32 2021 +1000
doc/groff.texi (Conditional Blocks): Clarify.
Make it explicit that good practice includes having multiple \} escapes
on a control line.
---
doc/groff.texi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/groff.texi b/doc/groff.texi
index 8bcacda..b4f436f 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -11923,9 +11923,9 @@ The above behavior may challenge the intuition; it was
implemented to
retain compatibility with @acronym{AT&T} @code{troff}. For clarity, it
is idiomatic to end input lines with @code{\@{}, followed by
@code{\@key{RET}} if desired to prevent the newline from being
-interpreted as a blank text line, and to have nothing more than a
-control character, spaces, and tabs preceding @code{\@}} on an input
-line.
+interpreted as a blank text line, and to precede @code{\@}} on an input
+line with nothing more than a control character, spaces, tabs, and other
+instances of itself.
@Example
.de DEBUG
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [groff] 10/17: doc/groff.texi (Conditional Blocks): Clarify.,
G. Branden Robinson <=