From 4cac2fc3fa46f66883ddc593b88e98f6961315e0 Mon Sep 17 00:00:00 2001 From: Andreas Schwab Date: Sun, 2 Feb 2003 17:31:49 +0000 Subject: [PATCH] (font-lock-match-c-style-declaration-item-and-skip-to-next): Don't require underscore in word before double open-paren. --- lisp/font-lock.el | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lisp/font-lock.el b/lisp/font-lock.el index cf47f77d40d..4dfad0e8f4f 100644 --- a/lisp/font-lock.el +++ b/lisp/font-lock.el @@ -1740,7 +1740,7 @@ Does not move further than LIMIT. The expected syntax of a declaration/definition item is `word' (preceded by optional whitespace and `*' characters and proceeded by optional whitespace) optionally followed by a `('. Everything following the item (but belonging to -it) is expected to by skip-able by `scan-sexps', and items are expected to be +it) is expected to be skip-able by `scan-sexps', and items are expected to be separated with a `,' and to be terminated with a `;'. Thus the regexp matches after point: word ( @@ -1759,7 +1759,7 @@ This function could be MATCHER in a MATCH-ANCHORED `font-lock-keywords' item." (let ((pos (point))) (skip-chars-backward " \t\n") (skip-syntax-backward "w") - (unless (looking-at "\\(\\sw+\\)[ \t\n]*\\sw*_\\sw*[ \t\n]*\\((\\)?") + (unless (looking-at "\\(\\sw+\\)[ \t\n]*\\sw+[ \t\n]*\\(((?\\)?") ;; Looks like it was something else, so go back to where we ;; were and reset the match data by rematching. (goto-char pos) -- 2.39.5