Clarify RX... semantics in manual (bug#58727)
Suggested by Michael Heerdegen. * doc/lispref/searching.texi (Rx Constructs): Explain implicit concatenation of `RX...`.
This commit is contained in:
parent
aa793512d0
commit
d083075b45
1 changed files with 6 additions and 2 deletions
|
|
@ -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.
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue