Subject: bug#11216: 23.4; parenthesis matching breaks on certain complex expressions

From: Andreas Schwab <[email-masked]>
Date: Wed, 11 Apr 2012 09:09:21 +0200

Nathan Trapuzzano <[email-masked]> writes:

> Matching gets messed up with the open parenthesis immediately following
> the first (?<!S\d). I suspect this is due to the opening double-quote
> about 10 characters later.

No, it's because < has open paren syntax, but there is no matching
close paren.  This is not a bug.  You need to use a suitable syntax
table that doesn't make < a paren syntax.

Andreas.

-- 
Andreas Schwab, [email-masked]
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."