GNU bug report logs - #11663
Incorrect regexp match with explicitly numbered blocks

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 11663 in the body.
You can then email your comments to 11663 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Vitalie Spinu <spinuvit <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Incorrect regexp match with explicitly numbered blocks 
Date: Sat, 09 Jun 2012 23:26:28 +0200

Hi, 

Assume this buffer's text. M-x regexp-builder and try this regexp
"\\(?:^Hi\\)" which works correctly. Modify to "\\(?2:^Hi\\)" and you
will see that ^ is taken literally and does not match bol anymore.

I've tried this in emacs 23 and on GNU Emacs 24.1.50.1
(i686-pc-linux-gnu, GTK+ Version 3.4.2) of 2012-06-08 on lakoocha,
modified by Debian.

Vitalie.

Message #10 received at 11663-done <at> debbugs.gnu.org (full text, mbox):

From: Andreas Schwab <schwab <at> linux-m68k.org>
To: Vitalie Spinu <spinuvit <at> gmail.com>
Cc: 11663-done <at> debbugs.gnu.org
Subject: Re: bug#11663: Incorrect regexp match with explicitly numbered blocks
Date: Sun, 10 Jun 2012 10:55:23 +0200

Thanks for the report.  The problem was that at_begline_loc_p wasn't
updated when the `(?N:' syntax was added.  I have also fixed a problem
with preceding backslashes that causes the ^ in patterns like "\\\\(^a)"
to be incorrectly taken non-literally.

Andreas.

-- 
Andreas Schwab, schwab <at> linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.