summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2022-04-02 13:20:56 +0300
committerEli Zaretskii <eliz@gnu.org>2022-04-02 13:20:56 +0300
commit9b5e9715ea64f971e215e91898e3ef49b159cdbe (patch)
tree21d4d5ed2685744e114f391be67c00c4810ec8a6
parent03e6a295d5c46151361845afbf5c8bcae915c89f (diff)
downloademacs-9b5e9715ea64f971e215e91898e3ef49b159cdbe.tar.gz
; * lisp/font-lock.el (font-lock-keywords): Doc fix.
-rw-r--r--lisp/font-lock.el10
1 files changed, 5 insertions, 5 deletions
diff --git a/lisp/font-lock.el b/lisp/font-lock.el
index 7d264cf9824..c9c390840ff 100644
--- a/lisp/font-lock.el
+++ b/lisp/font-lock.el
@@ -349,7 +349,7 @@ This can be an \"!\" or the \"n\" in \"ifndef\".")
;; Fontification variables:
(defvar font-lock-keywords nil
- "A list of the keywords to highlight.
+ "A list of keywords and corresponding font-lock highlighting rules.
There are two kinds of values: user-level, and compiled.
A user-level keywords list is what a major mode or the user would
@@ -374,10 +374,10 @@ point, and set `match-data' appropriately if 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 the keyword is (first) used in a buffer. This
-feature can be used to provide a keyword that can only be
-generated when Font Lock mode is actually turned on.
+FORM is an expression, whose value should be a keyword element
+of one of the above forms, evaluated when the keyword is (first)
+used in a buffer. This feature can be used to provide a keyword
+that can only be generated when Font Lock mode is actually turned on.
HIGHLIGHT should be either MATCH-HIGHLIGHT or MATCH-ANCHORED.