gbranden pushed a commit to branch master
in repository groff.
commit 03e8c3f4772ea2a68add511329b3a05a5096f063
Author: G. Branden Robinson <[email protected]>
AuthorDate: Thu Sep 22 17:44:55 2022 -0500
[docs]: Note another newline-as-delimiter fact.
It's true of opening delimiters too.
.tm .c=\n(.c, expected 1
A caf\o
e\(aa
in Paris
.tm .c=\n(.c, expected 5
.pl \n(nlu
---
doc/groff.texi | 5 ++---
man/groff.7.man | 4 ++--
2 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/doc/groff.texi b/doc/groff.texi
index bbbbcda1d..3e146b8e6 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -6908,9 +6908,8 @@ A few escape sequences,
@code{\o},
@code{\w},
@code{\X},
-and @code{\Z}, accept a newline as a delimiter. A newline that serves
-as an ending delimiter continues to be recognized as an input line
-ending.
+and @code{\Z}, accept a newline as a delimiter. Newlines that serve
+as delimiters continue to be recognized as input line terminators.
@Example
A caf\o
diff --git a/man/groff.7.man b/man/groff.7.man
index 2b64715df..455ad5858 100644
--- a/man/groff.7.man
+++ b/man/groff.7.man
@@ -3857,8 +3857,8 @@ and
.BR \[rs]Z ,
accept a newline as a delimiter.
.
-A newline that serves as an ending delimiter continues to be
-recognized as an input line ending.
+Newlines that serve as delimiters continue to be recognized as input
+line terminators.
.
Use of newlines as delimiters in escape sequences is also discouraged.
.
_______________________________________________
Groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit
