[groff] 41/49: groff(7): Relocate material.

[G. Branden Robinson]

gbranden pushed a commit to branch master
in repository groff.

commit 61ea39560f42561cce4bc8e3ea4d35d3ff02b73d
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Sun Sep 25 14:04:06 2022 -0500

    groff(7): Relocate material.
    
    Move section "Requests" in preparation for sync with our Texinfo manual.
---
 man/groff.7.man | 214 ++++++++++++++++++++++++++++----------------------------
 1 file changed, 107 insertions(+), 107 deletions(-)

diff --git a/man/groff.7.man b/man/groff.7.man
index 61e76f18f..1089563e8 100644
--- a/man/groff.7.man
+++ b/man/groff.7.man
@@ -1437,6 +1437,113 @@ which control character was used to call it.
 .
 .
 .\" ====================================================================
+.SH Requests
+.\" ====================================================================
+.
+.\" XXX: This is more of a groff_diff(7) sort of observation.
+In GNU
+.IR troff , \" GNU
+identifier names,
+including those of requests,
+can be arbitrarily long.
+.
+Unlike register and string interpolations,
+long request names require no specialized syntax.
+.
+.
+.\" BEGIN Keep (roughly) parallel with groff.texi node "Requests".
+.P
+Invoke a request by specifying its name after a control character and
+zero or more spaces or tabs.
+.
+The invocation of an unrecognized request is interpreted as a macro
+call.
+.
+Defining a macro with the same name as a request replaces the request.
+.
+Deleting a request name with the
+.request .rm
+request makes it unavailable.
+.
+Requests can be aliased with
+.request .als ,
+permitting them to be wrapped or non-destructively replaced.
+.
+.
+.P
+Most requests take one or more arguments.
+.
+Tabs are permitted after a request name and before its first argument
+(if any),
+but arguments themselves must be separated only by space characters.
+.
+(Plan\~9
+.I troff \" Plan 9
+allows tabs to separate arguments.)
+.
+There is no inherent limit on argument length or quantity.
+.
+Generally,
+a space
+.I within
+a request argument is not relevant,
+not meaningful,
+or is supported by bespoke provisions,
+as with the
+.request .tl
+request's delimiters.
+.
+Some requests,
+like
+.request .ds ,
+interpret the remainder of the control line as a single argument.
+.
+.
+.P
+Since spaces and tabs are ignored after a control character,
+they are commonly used to structure the source of documents or macro
+files with indentation.
+.
+.
+.P
+To prevent interpretation of a control character as such,
+prefix it with
+.RB \[lq] \[rs]& \[rq].
+.
+Since a control character is recognized only at the beginning of an
+input line or the branch of a control structure such as the
+.request .if
+request,
+this dummy character
+(or non-printing input break)
+evades that special context without affecting the output.
+.
+.
+.P
+Test the
+.register .br
+register inside a macro definition to determine which control character
+was used when calling it.
+.
+.
+.P
+There is no way to invoke an undefined request;
+such syntax is interpreted as a macro call instead.
+.
+If a macro of the desired name does not exist,
+it is created,
+assigned an empty definition,
+and a warning in category
+.RB \[lq] mac \[rq]
+is emitted.
+.
+Calling an undefined macro
+.I does
+end a macro definition naming it as its end macro.
+.\" END Keep (roughly) parallel with groff.texi node "Requests".
+.
+.
+.\" ====================================================================
 .SH "Control structures"
 .\" ====================================================================
 .
@@ -1809,113 +1916,6 @@ an increment or decrement is applied as if to\~0.
 .
 .
 .\" ====================================================================
-.SH Requests
-.\" ====================================================================
-.
-.\" XXX: This is more of a groff_diff(7) sort of observation.
-In GNU
-.IR troff , \" GNU
-identifier names,
-including those of requests,
-can be arbitrarily long.
-.
-Unlike register and string interpolations,
-long request names require no specialized syntax.
-.
-.
-.\" BEGIN Keep (roughly) parallel with groff.texi node "Requests".
-.P
-Invoke a request by specifying its name after a control character and
-zero or more spaces or tabs.
-.
-The invocation of an unrecognized request is interpreted as a macro
-call.
-.
-Defining a macro with the same name as a request replaces the request.
-.
-Deleting a request name with the
-.request .rm
-request makes it unavailable.
-.
-Requests can be aliased with
-.request .als ,
-permitting them to be wrapped or non-destructively replaced.
-.
-.
-.P
-Most requests take one or more arguments.
-.
-Tabs are permitted after a request name and before its first argument
-(if any),
-but arguments themselves must be separated only by space characters.
-.
-(Plan\~9
-.I troff \" Plan 9
-allows tabs to separate arguments.)
-.
-There is no inherent limit on argument length or quantity.
-.
-Generally,
-a space
-.I within
-a request argument is not relevant,
-not meaningful,
-or is supported by bespoke provisions,
-as with the
-.request .tl
-request's delimiters.
-.
-Some requests,
-like
-.request .ds ,
-interpret the remainder of the control line as a single argument.
-.
-.
-.P
-Since spaces and tabs are ignored after a control character,
-they are commonly used to structure the source of documents or macro
-files with indentation.
-.
-.
-.P
-To prevent interpretation of a control character as such,
-prefix it with
-.RB \[lq] \[rs]& \[rq].
-.
-Since a control character is recognized only at the beginning of an
-input line or the branch of a control structure such as the
-.request .if
-request,
-this dummy character
-(or non-printing input break)
-evades that special context without affecting the output.
-.
-.
-.P
-Test the
-.register .br
-register inside a macro definition to determine which control character
-was used when calling it.
-.
-.
-.P
-There is no way to invoke an undefined request;
-such syntax is interpreted as a macro call instead.
-.
-If a macro of the desired name does not exist,
-it is created,
-assigned an empty definition,
-and a warning in category
-.RB \[lq] mac \[rq]
-is emitted.
-.
-Calling an undefined macro
-.I does
-end a macro definition naming it as its end macro.
-.\" END Keep (roughly) parallel with groff.texi node "Requests".
-.
-.
-.\" ====================================================================
 .SS "Request short reference"
 .\" ====================================================================
 .