[Emacs-diffs] emacs/doc/lispref ChangeLog modes.texi

[Richard M. Stallman]

CVSROOT:        /cvsroot/emacs
Module name:    emacs
Changes by:     Richard M. Stallman <rms>       09/05/17 16:09:23

Modified files:
        doc/lispref    : ChangeLog modes.texi 

Log message:
        * modes.texi (Precalculated Fontification): Clarify text.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/emacs/doc/lispref/ChangeLog?cvsroot=emacs&r1=1.279&r2=1.280
http://cvs.savannah.gnu.org/viewcvs/emacs/doc/lispref/modes.texi?cvsroot=emacs&r1=1.14&r2=1.15

Patches:
Index: ChangeLog
===================================================================
RCS file: /cvsroot/emacs/emacs/doc/lispref/ChangeLog,v
retrieving revision 1.279
retrieving revision 1.280
diff -u -b -r1.279 -r1.280
--- ChangeLog   17 May 2009 12:11:18 -0000      1.279
+++ ChangeLog   17 May 2009 16:09:22 -0000      1.280
@@ -1,3 +1,7 @@
+2009-05-17  Richard M Stallman  <address@hidden>
+
+       * modes.texi (Precalculated Fontification): Clarify text.
+
 2009-05-17  Martin Rudalics  <address@hidden>
 
        * windows.texi (Selecting Windows): Clarify descriptions of

Index: modes.texi
===================================================================
RCS file: /cvsroot/emacs/emacs/doc/lispref/modes.texi,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -b -r1.14 -r1.15
--- modes.texi  29 Mar 2009 17:42:26 -0000      1.14
+++ modes.texi  17 May 2009 16:09:23 -0000      1.15
@@ -2864,18 +2864,21 @@
 @node Precalculated Fontification
 @subsection Precalculated Fontification
 
-  In addition to using @code{font-lock-defaults} for search-based
-fontification, you may use the special character property
address@hidden (@pxref{Special Properties}).  This property
-acts just like the explicit @code{face} property, but its activation
-is toggled when the user calls @kbd{M-x font-lock-mode}.  Using
address@hidden is especially convenient for special modes
-which construct their text programmatically, such as
address@hidden and @code{occur}.
-
-If your mode does not use any of the other machinery of Font Lock
-(i.e. it only uses the @code{font-lock-face} property), it should not
-set the variable @code{font-lock-defaults}.
+  Some major modes such as @code{list-buffers} and @code{occur}
+construct the buffer text programmatically.  The easiest way for them
+to support Font Lock mode is to specify the faces of text when they
+insert the text in the buffer.
+
+  The way to do this is to specify the faces in the text with the
+special text property @code{font-lock-face} (@pxref{Special
+Properties}).  When Font Lock mode is enabled, this property controls
+the display, just like the @code{face} property.  When Font Lock mode
+is disabled, @code{font-lock-face} has no effect on the display.
+
+  It is ok for a mode to use @code{font-lock-face} for some text and
+also use the normal Font Lock machinery.  But if the mode does not use
+the normal Font Lock machinery, it should not set the variable
address@hidden
 
 @node Faces for Font Lock
 @subsection Faces for Font Lock