[groff] 40/49: groff_tmac(5): Drop "Copy mode" subsection.

[G. Branden Robinson]

gbranden pushed a commit to branch master
in repository groff.

commit 42735e58af80be8c5031ee90374f8c076d9ae30a
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Thu Jun 17 07:29:06 2021 +1000

    groff_tmac(5): Drop "Copy mode" subsection.
    
    It is mostly redundant with the "Copy mode" section of groff(7) and our
    Texinfo manual.  This page in general has a scope control problem.
---
 man/groff_tmac.5.man | 105 ---------------------------------------------------
 1 file changed, 105 deletions(-)

diff --git a/man/groff_tmac.5.man b/man/groff_tmac.5.man
index 0c5c87b..9552c91 100644
--- a/man/groff_tmac.5.man
+++ b/man/groff_tmac.5.man
@@ -984,111 +984,6 @@ see
 .
 .
 .\" ====================================================================
-.SS "Copy mode"
-.\" ====================================================================
-.
-When
-.I groff
-processes certain requests,
-most importantly those which define a macro,
-string,
-or diversion,
-it does so in
-.IR "copy mode" :
-it copies the characters of the definition into a dedicated storage
-region,
-interpolating the escape sequences
-.BR \[rs]n ,
-.BR \[rs]$ ,
-and
-.BR \[rs]* ,
-intepreting
-.B \[rs]\[rs]
-and
-.BI \[rs] newline
-immediately,
-and storing all other escape sequences in an encoded form.
-.
-.
-.P
-In this phase, groff interprets all backslashes; that means that all
-escape sequences in the macro body are interpreted and replaced by
-their value.
-.
-For constant expressions, this is wanted, but strings and registers
-that might change between calls of the macro must be protected from
-being evaluated.
-.
-This is most easily done by doubling the backslash that introduces the
-escape sequence.
-.
-This doubling is most important for the positional parameters.
-.
-For example, the following macro prints information on its arguments:
-.
-.
-.IP
-.ds @1 \[rs]f[I]\[rs]\[rs]$0\[rs]f[]\"
-.ds @2 arguments:\"
-.EX
-\&.ds midpart was called with the following
-\&.de print_args
-\&\*[@1]\ \[rs]*[midpart]\ \[rs]\[rs]n[.$]\ \*[@2]
-\&\[rs]\[rs]$*
-\&..
-.EE
-.rm @1
-.rm @2
-.
-.
-.P
-When calling this macro by
-.
-.IP
-.EX
-\&.print_args arg1 arg2
-.EE
-.
-.P
-the following text is printed:
-.
-.IP
-.EX
-\&\f[CI]print_args\f[] was called with the following 2 arguments: arg1 arg2
-.EE
-.
-.
-.P
-Let's analyze each backslash in the macro definition.
-.
-As the positional parameters and the number of arguments change
-with each call of the macro their leading backslash must be doubled,
-which results in
-.RI \[rs]\[rs] $*
-and
-.RI \[rs]\[rs] [.$] .
-The same applies to the macro name because it could be called with an
-alias, so
-.RI \[rs]\[rs] $0 .
-.
-.
-.P
-On the other hand,
-.I midpart
-is a constant string, it does not change, so no doubling for
-.RI \[rs] *[midpart] .
-The
-.RI \[rs] f
-escape sequences are predefined groff elements for setting the font
-within the text.
-.
-Of course, this behavior does not change, so no doubling with
-.RI \[rs] f[I]
-and
-.RI \[rs] f[] .
-.
-.
-.\" ====================================================================
 .SS "Draft mode"
 .\" ====================================================================
 .