groff-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[groff] 15/20: [doc,man]: Clarify escape sequence syntax.


From: G. Branden Robinson
Subject: [groff] 15/20: [doc,man]: Clarify escape sequence syntax.
Date: Mon, 21 Oct 2024 20:14:53 -0400 (EDT)

gbranden pushed a commit to branch master
in repository groff.

commit a4f71658391b2fc2a1a7399aa0834c5e7f2648e4
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Sat Oct 19 04:34:16 2024 -0500

    [doc,man]: Clarify escape sequence syntax.
---
 doc/groff.texi.in | 6 +++---
 man/groff.7.man   | 3 ++-
 2 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/doc/groff.texi.in b/doc/groff.texi.in
index 1564c732d..0f0c9ac1b 100644
--- a/doc/groff.texi.in
+++ b/doc/groff.texi.in
@@ -7073,9 +7073,9 @@ of the foregoing conventions (@code{\s}), designate their 
own
 termination sequence (@code{\?}), consume input until the next newline
 (@code{\!}, @code{\"}, @code{\#}), or support an additional modifier
 character (@code{\s} again, and @code{\n}).  In no case can an escape
-sequence parameter contain a newline.  As with requests, use of some
-escape sequences in source documents may interact poorly with a macro
-package you use; consult its documentation to learn of ``safe''
+sequence parameter contain an unescaped newline.  As with requests, use
+of some escape sequences in source documents may interact poorly with a
+macro package you use; consult its documentation to learn of ``safe''
 sequences or alternative facilities it provides to achieve the desired
 result.
 
diff --git a/man/groff.7.man b/man/groff.7.man
index 47dfbe2df..7ba0616bf 100644
--- a/man/groff.7.man
+++ b/man/groff.7.man
@@ -1676,7 +1676,8 @@ again,
 and
 .BR \|\[rs]n ).
 .
-In no case can an escape sequence parameter contain a newline.
+In no case can an escape sequence parameter contain an unescaped
+newline.
 .\" As with requests, use of some escape sequences in source documents
 .\" may interact poorly with a macro package you use; consult its
 .\" documentation to learn of ``safe'' sequences or alternative



reply via email to

[Prev in Thread] Current Thread [Next in Thread]