[Emacs-diffs] fix/bug-31311-pcase-doc f870e5e 3/6: move UPattern and QPattern tables outside of @defmac pcase

[Thien-Thi Nguyen]

branch: fix/bug-31311-pcase-doc
commit f870e5e7660253f37befceca5c1a4ed3725360e4
Author: Thien-Thi Nguyen <address@hidden>
Commit: Thien-Thi Nguyen <address@hidden>

    move UPattern and QPattern tables outside of @defmac pcase
    
    this results in more efficient horizontal space usage
---
 doc/lispref/control.texi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/lispref/control.texi b/doc/lispref/control.texi
index 492f188..dcfb27f 100644
--- a/doc/lispref/control.texi
+++ b/doc/lispref/control.texi
@@ -325,6 +325,8 @@ The @var{pattern} part of a clause can be of one of two 
types:
 @dfn{UPattern}, which is not quoted.  UPatterns are simpler, so we
 describe them first.
 
address@hidden defmac
+
 Note: In the description of the patterns below, we use ``the value
 being matched'' to refer to the value of the @var{expression} that is
 the first argument of @code{pcase}.
@@ -456,8 +458,6 @@ in many cases lead to a more readable code.
 @c FIXME: There should be an example here showing how a 'pcase' that
 @c uses QPatterns can be rewritten using UPatterns.
 
address@hidden defmac
-
 Here is an example of using @code{pcase} to implement a simple
 interpreter for a little expression language (note that this example
 requires lexical binding, @pxref{Lexical Binding}):