From d083075b458ac532e114e6af09e990fba422d0ed Mon Sep 17 00:00:00 2001 From: =?utf8?q?Mattias=20Engdeg=C3=A5rd?= Date: Mon, 24 Oct 2022 12:35:47 +0200 Subject: [PATCH] Clarify RX... semantics in manual (bug#58727) Suggested by Michael Heerdegen. * doc/lispref/searching.texi (Rx Constructs): Explain implicit concatenation of `RX...`. --- doc/lispref/searching.texi | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/doc/lispref/searching.texi b/doc/lispref/searching.texi index 5ee139a11d3..88b3b83f8eb 100644 --- a/doc/lispref/searching.texi +++ b/doc/lispref/searching.texi @@ -1052,8 +1052,12 @@ customization. @subsubsection Constructs in @code{rx} regexps The various forms in @code{rx} regexps are described below. The -shorthand @var{rx} represents any @code{rx} form, and @var{rx}@dots{} -means zero or more @code{rx} forms. These are all valid arguments to +shorthand @var{rx} represents any @code{rx} form. @var{rx}@dots{} +means zero or more @code{rx} forms and, unless stated otherwise, +matches these forms in sequence as if wrapped in a @code{(seq @dots{})} +subform. + +These are all valid arguments to the @code{rx} macro. Where the corresponding string regexp syntax is given, @var{A}, @var{B}, @dots{} are string regexp subexpressions. -- 2.39.2