aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGlenn Morris2008-09-20 20:16:29 +0000
committerGlenn Morris2008-09-20 20:16:29 +0000
commit8230b7b3a110f388ee09873a8726f5a465d53abf (patch)
treeaeefdf7732ea3b145518480d7d310ba2349884fc
parent3d53e905e68d0a473915d025a474fb9ac62106f1 (diff)
downloademacs-8230b7b3a110f388ee09873a8726f5a465d53abf.tar.gz
emacs-8230b7b3a110f388ee09873a8726f5a465d53abf.zip
Comment.
-rw-r--r--lisp/font-lock.el5
1 files changed, 5 insertions, 0 deletions
diff --git a/lisp/font-lock.el b/lisp/font-lock.el
index 3f81de0b144..dc1af6c61d7 100644
--- a/lisp/font-lock.el
+++ b/lisp/font-lock.el
@@ -288,6 +288,11 @@ If a number, only buffers greater than this size have fontification messages."
288;; We now allow a FACENAME in `font-lock-keywords' to be any expression that 288;; We now allow a FACENAME in `font-lock-keywords' to be any expression that
289;; returns a face. So the easiest thing is to continue using these variables, 289;; returns a face. So the easiest thing is to continue using these variables,
290;; rather than sometimes evaling FACENAME and sometimes not. sm. 290;; rather than sometimes evaling FACENAME and sometimes not. sm.
291
292;; Note that in new code, in the vast majority of cases there is no
293;; need to create variables that specify face names. Simply using
294;; faces directly is enough. Font-lock is not a template to be
295;; followed in this area.
291(defvar font-lock-comment-face 'font-lock-comment-face 296(defvar font-lock-comment-face 'font-lock-comment-face
292 "Face name to use for comments.") 297 "Face name to use for comments.")
293 298