From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Shy groups and * ...eh, what?
Date: Sat, 22 Oct 2022 08:39:02 +0200 [thread overview]
Message-ID: <Y1OQBhMUdRfzrLnX@tuxteam.de> (raw)
In-Reply-To: <87edv0mqns.fsf@web.de>
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
On Sat, Oct 22, 2022 at 06:24:39AM +0200, Michael Heerdegen wrote:
> Hello,
>
> I wanted to be sure I correctly understood that if you give multiple RX
> arguments to the `rx' `*' operator, they are implicitly interpreted as a
> sequence (AFAIU, that's the case. An implicit `or' would also make
> sense, that's why I wondered).
I didn't try to repeat your examples, but you are right: there is at least
a big smoking hole in the docs: all of the repetition operators seem to
take zero (one?) or more arguments according to the syntax shorthand, but
the text refers to just one term, like here:
‘(zero-or-more RX...)’
‘(0+ RX...)’
Match the RXs zero or more times. Greedy by default.
Corresponding string regexp: ‘A*’ (greedy), ‘A*?’ (non-greedy)
...what is this `A' the text is referring to? Your experiments suggest
that it is the sequence of the `RX...' in the syntax shorthand (i.e.
(seq RX...), but the docs just leave it open :)
Cheers
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-10-22 6:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 4:24 Shy groups and * ...eh, what? Michael Heerdegen
2022-10-22 6:11 ` Heime
2022-10-22 6:39 ` tomas [this message]
2022-10-23 2:47 ` Michael Heerdegen
2022-10-24 4:45 ` tomas
2022-10-24 21:01 ` Emanuel Berg
2022-10-25 3:12 ` Michael Heerdegen
2022-10-25 3:44 ` Emanuel Berg
2022-10-25 4:43 ` tomas
2022-10-22 6:49 ` Heime
2022-10-22 7:37 ` Michael Heerdegen
2022-10-22 8:34 ` tomas
2022-10-22 8:41 ` Michael Heerdegen
2022-10-22 11:12 ` Bruno Barbier
2022-10-23 2:45 ` Michael Heerdegen
2022-10-24 4:27 ` Emanuel Berg
2022-10-22 19:54 ` [External] : " Drew Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y1OQBhMUdRfzrLnX@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).