From: Andreas Schwab <schwab@linux-m68k.org>
To: Joe Corneli <holtzermann17@gmail.com>
Cc: emacs-pretest-bug@gnu.org, 2881@emacsbugs.donarmstrong.com
Subject: bug#2881: 23.0.91; inconsistent regexps with "explicitly numbered group"
Date: Fri, 03 Apr 2009 21:55:42 +0200 [thread overview]
Message-ID: <m2ljqh5x6p.fsf@igel.home> (raw)
In-Reply-To: <a9670630904031215w611793edw73da994f48bf607b@mail.gmail.com> (Joe Corneli's message of "Fri, 3 Apr 2009 15:15:01 -0400")
Joe Corneli <holtzermann17@gmail.com> writes:
> Please execute the following forms with C-x C-e. Form 1
> and Form 3 return `t' (Yes, we are looking at the
> indicated regular expression), whereas Form 2 returns
> `nil' (even though from the Elisp reference page "34.3.1.3
> Backslash Constructs in Regular Expressions", it appears
> that this form ought to return `t' like the others).
`\|' applies to the largest possible surrounding expressions.
Only a surrounding `\( ... \)' grouping can limit the grouping
power of `\|'.
> (let ((possible-environments
> "\\(?1:lisp\\)\\|\\(?1:idea\\)\\|\\(?1:common\\)") )
> (looking-at
> (concat "\n*?\\\\begin{"
> possible-environments
> "}")))
The three alternatives of this regexp are "\n*?\\\\begin{\\(?1:lisp\\)",
"\\(?1:idea\\)" and "\\(?1:common\\)".
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2009-04-03 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jwvocvdct45.fsf-monnier+emacsbugreports@gnu.org>
2009-04-03 19:15 ` bug#2881: 23.0.91; inconsistent regexps with "explicitly numbered group" Joe Corneli
2009-04-03 19:55 ` Andreas Schwab [this message]
2009-04-03 20:41 ` Joe Corneli
2009-04-03 21:32 ` Andreas Schwab
2009-04-03 21:38 ` Joe Corneli
2009-04-03 21:50 ` bug#2881: marked as done (23.0.91; inconsistent regexps with "explicitly numbered group") Emacs bug Tracking System
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2ljqh5x6p.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=2881@emacsbugs.donarmstrong.com \
--cc=emacs-pretest-bug@gnu.org \
--cc=holtzermann17@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.