summaryrefslogtreecommitdiff
path: root/lisp/font-lock.el
diff options
context:
space:
mode:
authorStefan Monnier <monnier@iro.umontreal.ca>2004-07-27 18:45:41 +0000
committerStefan Monnier <monnier@iro.umontreal.ca>2004-07-27 18:45:41 +0000
commitf9c0bc2e7385ea561827f9e99d689d44ff7b0640 (patch)
tree0f011d88344498f09360965c718029ab757bbf1e /lisp/font-lock.el
parent47a97a6db31119476194b4bb9f32d1891a3a2d1f (diff)
downloademacs-f9c0bc2e7385ea561827f9e99d689d44ff7b0640.tar.gz
(font-lock-keywords): Docstring improvement.
Diffstat (limited to 'lisp/font-lock.el')
-rw-r--r--lisp/font-lock.el5
1 files changed, 3 insertions, 2 deletions
diff --git a/lisp/font-lock.el b/lisp/font-lock.el
index 36dac14f6a9..8cb43bc0bd8 100644
--- a/lisp/font-lock.el
+++ b/lisp/font-lock.el
@@ -358,8 +358,9 @@ Each element in a user-level keywords list should have one of these forms:
(eval . FORM)
where MATCHER can be either the regexp to search for, or the function name to
-call to make the search (called with one argument, the limit of the search) and
-return non-nil if it succeeds (and set `match-data' appropriately).
+call to make the search (called with one argument, the limit of the search;
+it should return non-nil, move point, and set `match-data' appropriately iff
+it succeeds; like `re-search-forward' would).
MATCHER regexps can be generated via the function `regexp-opt'.
FORM is an expression, whose value should be a keyword element, evaluated when