From: Stefan Monnier <monnier@iro.umontreal.ca>
Date: Tue, 27 Jul 2004 18:45:41 +0000 (+0000)
Subject: (font-lock-keywords): Docstring improvement.
X-Git-Tag: ttn-vms-21-2-B4~5381
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=f9c0bc2e7385ea561827f9e99d689d44ff7b0640;p=emacs.git

(font-lock-keywords): Docstring improvement.
---

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