groff-commit
[Top][All Lists]
Advanced

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

[groff] 06/11: [docs]: Clarify a point of escape sequence syntax.


From: G. Branden Robinson
Subject: [groff] 06/11: [docs]: Clarify a point of escape sequence syntax.
Date: Wed, 13 Mar 2024 16:16:25 -0400 (EDT)

gbranden pushed a commit to branch master
in repository groff.

commit ba8081aab428f3e29bb8216a21020dfdad30399a
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Sun Mar 10 00:32:23 2024 -0600

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

diff --git a/doc/groff.texi.in b/doc/groff.texi.in
index 907c0c537..06dc0a036 100644
--- a/doc/groff.texi.in
+++ b/doc/groff.texi.in
@@ -7069,9 +7069,10 @@ character.  A few escape sequences are idiosyncratic, 
and support both
 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}).  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''
+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''
 sequences or alternative facilities it provides to achieve the desired
 result.
 
diff --git a/man/groff.7.man b/man/groff.7.man
index 0278e0df2..3c78f8a1a 100644
--- a/man/groff.7.man
+++ b/man/groff.7.man
@@ -1678,6 +1678,8 @@ or support an additional modifier character
 again,
 and
 .BR \|\[rs]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'' sequences or alternative



reply via email to

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