summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndreas Schwab <schwab@suse.de>2003-02-02 17:31:49 +0000
committerAndreas Schwab <schwab@suse.de>2003-02-02 17:31:49 +0000
commit49ab1a70d1be5a8f4b9238728722dbfa4b086528 (patch)
treecff4c058fc9ee866d63c08209257da17839abb0b
parent64699b78b9b0f9b016695f35b408d901ddcffac5 (diff)
downloademacs-49ab1a70d1be5a8f4b9238728722dbfa4b086528.tar.gz
(font-lock-match-c-style-declaration-item-and-skip-to-next):
Don't require underscore in word before double open-paren.
-rw-r--r--lisp/font-lock.el4
1 files 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)