groff-commit
[Top][All Lists]
Advanced

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

[groff] 12/50: [docs]: Fix omission: \? interpreted in copy mode.


From: G. Branden Robinson
Subject: [groff] 12/50: [docs]: Fix omission: \? interpreted in copy mode.
Date: Sat, 21 May 2022 12:17:24 -0400 (EDT)

gbranden pushed a commit to branch master
in repository groff.

commit e3c0f8207d29e8da141dbde35cf52bdf08023c67
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Tue May 17 17:23:50 2022 -0500

    [docs]: Fix omission: \? interpreted in copy mode.
    
    * doc/groff.texi (Copy Mode):
    * man/groff.7.man (Copy mode): Fix omission; `\?` is interpreted in copy
      mode.
---
 ChangeLog       |  6 ++++++
 doc/groff.texi  | 11 ++++++-----
 man/groff.7.man |  9 ++++++---
 3 files changed, 18 insertions(+), 8 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 8f51dcfa..0ed4e7bb 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2022-05-17  G. Branden Robinson <g.branden.robinson@gmail.com>
+
+       * doc/groff.texi (Copy Mode):
+       * man/groff.7.man (Copy mode): Fix omission; `\?` is interpreted
+       in copy mode.
+
 2022-05-17  G. Branden Robinson <g.branden.robinson@gmail.com>
 
        * tmac/s.tmac (PT): Unclutter name space; remove
diff --git a/doc/groff.texi b/doc/groff.texi
index 193547e5..27e0d6f3 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -12984,7 +12984,7 @@ When GNU @code{troff} processes certain requests, most 
importantly those
 which define or append to a macro or string, it does so in @dfn{copy
 mode}: it copies the characters of the definition into a dedicated
 storage region, interpolating the escape sequences @code{\n}, @code{\g},
-@code{\$}, @code{\*}, and @code{\V} normally; interpreting
+@code{\$}, @code{\*}, @code{\V}, and @code{\?} normally; interpreting
 @code{\@key{RET}} immediately; discarding comments @code{\"} and
 @code{\#}; interpolating the current leader, escape, or tab character
 with @code{\a}, @code{\e}, and @code{\t}, respectively; and storing all
@@ -13001,8 +13001,8 @@ processed immediately upon recognition, can be termed
 @Defesc {\\\\, , , }
 The escape character, @code{\} by default, can escape a backslash.  This
 enables you to control whether a given @code{\n}, @code{\g}, @code{\$},
-@code{\*}, or @code{\V} escape sequence is interpreted at the time the
-macro containing it is defined, or later when the macro is
+@code{\*}, @code{\V}, or @code{\?}  escape sequence is interpreted at
+the time the macro containing it is defined, or later when the macro is
 called.@footnote{Compare this to the @code{\def} and @code{\edef}
 commands in @TeX{}.}
 
@@ -13084,8 +13084,9 @@ Each escape character is interpreted twice---once in 
copy mode, when the
 macro is defined, and once outside of it, when the macro is called.  As
 seen above, this fact leads to exponential growth in the quantity of
 escape characters required to delay interpolation of @code{\n},
-@code{\g}, @code{\$}, @code{\*}, and @code{\V} at each nesting level,
-which can be daunting.  GNU @code{troff} offers a solution.
+@code{\g}, @code{\$}, @code{\*}, @code{\V}, and @code{\?} at each
+nesting level, which can be daunting.  GNU @code{troff} offers a
+solution.
 
 @Defesc {\\E, , , }
 @code{\E} represents an escape character that is not interpreted in copy
diff --git a/man/groff.7.man b/man/groff.7.man
index 5201dbd4..0b40a1b6 100644
--- a/man/groff.7.man
+++ b/man/groff.7.man
@@ -5688,8 +5688,9 @@ interpolating the escape sequences
 .BR \[rs]g ,
 .BR \[rs]$ ,
 .BR \[rs]* ,
+.BR \[rs]V ,
 and
-.B \[rs]V
+.B \[rs]?\&
 normally;
 interpreting
 .BI \[rs] newline
@@ -5730,8 +5731,9 @@ This enables you to control whether a given
 .BR \[rs]g ,
 .BR \[rs]$ ,
 .BR \[rs]* ,
+.BR \[rs]V ,
 or
-.B \[rs]V
+.B \[rs]?\&
 escape sequence is interpreted at the time the macro containing it is
 defined,
 or later when the macro is called.
@@ -5810,8 +5812,9 @@ characters required to delay interpolation of
 .BR \[rs]g ,
 .BR \[rs]$ ,
 .BR \[rs]* ,
+.BR \[rs]V ,
 and
-.B \[rs]V
+.B \[rs]?\&
 at each nesting level.
 .
 An alternative is to use



reply via email to

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