| blob | fe873297dc2e7cf0efc49e89ed8b58f262c4acbb |
1 ;;; font-lock.el --- Electric font lock mode
3 ;; Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
4 ;; 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
5 ;; 2010 Free Software Foundation, Inc.
7 ;; Author: Jamie Zawinski
8 ;; Richard Stallman
9 ;; Stefan Monnier
10 ;; Maintainer: FSF
11 ;; Keywords: languages, faces
12 ;; Package: emacs
14 ;; This file is part of GNU Emacs.
16 ;; GNU Emacs is free software: you can redistribute it and/or modify
17 ;; it under the terms of the GNU General Public License as published by
18 ;; the Free Software Foundation, either version 3 of the License, or
19 ;; (at your option) any later version.
21 ;; GNU Emacs is distributed in the hope that it will be useful,
22 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
23 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
24 ;; GNU General Public License for more details.
26 ;; You should have received a copy of the GNU General Public License
27 ;; along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.
29 ;;; Commentary:
31 ;; Font Lock mode is a minor mode that causes your comments to be displayed in
32 ;; one face, strings in another, reserved words in another, and so on.
33 ;;
34 ;; Comments will be displayed in `font-lock-comment-face'.
35 ;; Strings will be displayed in `font-lock-string-face'.
36 ;; Regexps are used to display selected patterns in other faces.
37 ;;
38 ;; To make the text you type be fontified, use M-x font-lock-mode RET.
39 ;; When this minor mode is on, the faces of the current line are updated with
40 ;; every insertion or deletion.
41 ;;
42 ;; To turn Font Lock mode on automatically, add this to your ~/.emacs file:
43 ;;
44 ;; (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
45 ;;
46 ;; Or if you want to turn Font Lock mode on in many modes:
47 ;;
48 ;; (global-font-lock-mode t)
49 ;;
50 ;; Fontification for a particular mode may be available in a number of levels
51 ;; of decoration. The higher the level, the more decoration, but the more time
52 ;; it takes to fontify. See the variable `font-lock-maximum-decoration', and
53 ;; also the variable `font-lock-maximum-size'. Support modes for Font Lock
54 ;; mode can be used to speed up Font Lock mode. See `font-lock-support-mode'.
55 \f
56 ;;; How Font Lock mode fontifies:
58 ;; When Font Lock mode is turned on in a buffer, it (a) fontifies the entire
59 ;; buffer and (b) installs one of its fontification functions on one of the
60 ;; hook variables that are run by Emacs after every buffer change (i.e., an
61 ;; insertion or deletion). Fontification means the replacement of `face' text
62 ;; properties in a given region; Emacs displays text with these `face' text
63 ;; properties appropriately.
64 ;;
65 ;; Fontification normally involves syntactic (i.e., strings and comments) and
66 ;; regexp (i.e., keywords and everything else) passes. There are actually
67 ;; three passes; (a) the syntactic keyword pass, (b) the syntactic pass and (c)
68 ;; the keyword pass. Confused?
69 ;;
70 ;; The syntactic keyword pass places `syntax-table' text properties in the
71 ;; buffer according to the variable `font-lock-syntactic-keywords'. It is
72 ;; necessary because Emacs' syntax table is not powerful enough to describe all
73 ;; the different syntactic constructs required by the sort of people who decide
74 ;; that a single quote can be syntactic or not depending on the time of day.
75 ;; (What sort of person could decide to overload the meaning of a quote?)
76 ;; Obviously the syntactic keyword pass must occur before the syntactic pass.
77 ;;
78 ;; The syntactic pass places `face' text properties in the buffer according to
79 ;; syntactic context, i.e., according to the buffer's syntax table and buffer
80 ;; text's `syntax-table' text properties. It involves using a syntax parsing
81 ;; function to determine the context of different parts of a region of text. A
82 ;; syntax parsing function is necessary because generally strings and/or
83 ;; comments can span lines, and so the context of a given region is not
84 ;; necessarily apparent from the content of that region. Because the keyword
85 ;; pass only works within a given region, it is not generally appropriate for
86 ;; syntactic fontification. This is the first fontification pass that makes
87 ;; changes visible to the user; it fontifies strings and comments.
88 ;;
89 ;; The keyword pass places `face' text properties in the buffer according to
90 ;; the variable `font-lock-keywords'. It involves searching for given regexps
91 ;; (or calling given search functions) within the given region. This is the
92 ;; second fontification pass that makes changes visible to the user; it
93 ;; fontifies language reserved words, etc.
94 ;;
95 ;; Oh, and the answer is, "Yes, obviously just about everything should be done
96 ;; in a single syntactic pass, but the only syntactic parser available
97 ;; understands only strings and comments." Perhaps one day someone will write
98 ;; some syntactic parsers for common languages and a son-of-font-lock.el could
99 ;; use them rather then relying so heavily on the keyword (regexp) pass.
101 ;;; How Font Lock mode supports modes or is supported by modes:
103 ;; Modes that support Font Lock mode do so by defining one or more variables
104 ;; whose values specify the fontification. Font Lock mode knows of these
105 ;; variable names from the buffer local variable `font-lock-defaults'.
106 ;; (Font Lock mode is set up via (a) where a mode's patterns are
107 ;; distributed with the mode's package library, and (b) where a mode's
108 ;; patterns are distributed with font-lock.el itself. An example of (a)
109 ;; is Pascal mode, an example of (b) is Lisp mode. Normally, the mechanism is
110 ;; (a); (b) is used where it is not clear which package library should contain
111 ;; the pattern definitions.) Font Lock mode chooses which variable to use for
112 ;; fontification based on `font-lock-maximum-decoration'.
113 ;;
114 ;; Font Lock mode fontification behavior can be modified in a number of ways.
115 ;; See the below comments and the comments distributed throughout this file.
117 ;;; Constructing patterns:
119 ;; See the documentation for the variable `font-lock-keywords'.
120 ;;
121 ;; Efficient regexps for use as MATCHERs for `font-lock-keywords' and
122 ;; `font-lock-syntactic-keywords' can be generated via the function
123 ;; `regexp-opt'.
125 ;;; Adding patterns for modes that already support Font Lock:
127 ;; Though Font Lock highlighting patterns already exist for many modes, it's
128 ;; likely there's something that you want fontified that currently isn't, even
129 ;; at the maximum fontification level. You can add highlighting patterns via
130 ;; `font-lock-add-keywords'. For example, say in some C
131 ;; header file you #define the token `and' to expand to `&&', etc., to make
132 ;; your C code almost readable. In your ~/.emacs there could be:
133 ;;
134 ;; (font-lock-add-keywords 'c-mode '("\\<\\(and\\|or\\|not\\)\\>"))
135 ;;
136 ;; Some modes provide specific ways to modify patterns based on the values of
137 ;; other variables. For example, additional C types can be specified via the
138 ;; variable `c-font-lock-extra-types'.
140 ;;; Adding patterns for modes that do not support Font Lock:
142 ;; Not all modes support Font Lock mode. If you (as a user of the mode) add
143 ;; patterns for a new mode, you must define in your ~/.emacs a variable or
144 ;; variables that specify regexp fontification. Then, you should indicate to
145 ;; Font Lock mode, via the mode hook setting `font-lock-defaults', exactly what
146 ;; support is required. For example, say Foo mode should have the following
147 ;; regexps fontified case-sensitively, and comments and strings should not be
148 ;; fontified automagically. In your ~/.emacs there could be:
149 ;;
150 ;; (defvar foo-font-lock-keywords
151 ;; '(("\\<\\(one\\|two\\|three\\)\\>" . font-lock-keyword-face)
152 ;; ("\\<\\(four\\|five\\|six\\)\\>" . font-lock-type-face))
153 ;; "Default expressions to highlight in Foo mode.")
154 ;;
155 ;; (add-hook 'foo-mode-hook
156 ;; (lambda ()
157 ;; (set (make-local-variable 'font-lock-defaults)
158 ;; '(foo-font-lock-keywords t))))
160 ;;; Adding Font Lock support for modes:
162 ;; Of course, it would be better that the mode already supports Font Lock mode.
163 ;; The package author would do something similar to above. The mode must
164 ;; define at the top-level a variable or variables that specify regexp
165 ;; fontification. Then, the mode command should indicate to Font Lock mode,
166 ;; via `font-lock-defaults', exactly what support is required. For example,
167 ;; say Bar mode should have the following regexps fontified case-insensitively,
168 ;; and comments and strings should be fontified automagically. In bar.el there
169 ;; could be:
170 ;;
171 ;; (defvar bar-font-lock-keywords
172 ;; '(("\\<\\(uno\\|due\\|tre\\)\\>" . font-lock-keyword-face)
173 ;; ("\\<\\(quattro\\|cinque\\|sei\\)\\>" . font-lock-type-face))
174 ;; "Default expressions to highlight in Bar mode.")
175 ;;
176 ;; and within `bar-mode' there could be:
177 ;;
178 ;; (set (make-local-variable 'font-lock-defaults)
179 ;; '(bar-font-lock-keywords nil t))
180 \f
181 ;; What is fontification for? You might say, "It's to make my code look nice."
182 ;; I think it should be for adding information in the form of cues. These cues
183 ;; should provide you with enough information to both (a) distinguish between
184 ;; different items, and (b) identify the item meanings, without having to read
185 ;; the items and think about it. Therefore, fontification allows you to think
186 ;; less about, say, the structure of code, and more about, say, why the code
187 ;; doesn't work. Or maybe it allows you to think less and drift off to sleep.
188 ;;
189 ;; So, here are my opinions/advice/guidelines:
190 ;;
191 ;; - Highlight conceptual objects, such as function and variable names, and
192 ;; different objects types differently, i.e., (a) and (b) above, highlight
193 ;; function names differently to variable names.
194 ;; - Keep the faces distinct from each other as far as possible.
195 ;; i.e., (a) above.
196 ;; - Use the same face for the same conceptual object, across all modes.
197 ;; i.e., (b) above, all modes that have items that can be thought of as, say,
198 ;; keywords, should be highlighted with the same face, etc.
199 ;; - Make the face attributes fit the concept as far as possible.
200 ;; i.e., function names might be a bold color such as blue, comments might
201 ;; be a bright color such as red, character strings might be brown, because,
202 ;; err, strings are brown (that was not the reason, please believe me).
203 ;; - Don't use a non-nil OVERRIDE unless you have a good reason.
204 ;; Only use OVERRIDE for special things that are easy to define, such as the
205 ;; way `...' quotes are treated in strings and comments in Emacs Lisp mode.
206 ;; Don't use it to, say, highlight keywords in commented out code or strings.
207 ;; - Err, that's it.
208 \f
209 ;;; Code:
214 ;; Define core `font-lock' group.
216 "Font Lock mode text highlighting package."
222 "Faces for highlighting text."
227 "Extra mode-specific type names for highlighting declarations."
229 \f
230 ;; User variables.
233 "Maximum size of a buffer for buffer fontification.
234 Only buffers less than this can be fontified when Font Lock mode is turned on.
235 If nil, means size is irrelevant.
236 If a list, each element should be a cons pair of the form (MAJOR-MODE . SIZE),
237 where MAJOR-MODE is a symbol or t (meaning the default). For example:
238 ((c-mode . 256000) (c++-mode . 256000) (rmail-mode . 1048576))
239 means that the maximum size is 250K for buffers in C or C++ modes, one megabyte
240 for buffers in Rmail mode, and size is irrelevant otherwise."
255 "Maximum decoration level for fontification.
256 If nil, use the default decoration (typically the minimum available).
257 If t, use the maximum decoration available.
258 If a number, use that level of decoration (or if not available the maximum).
259 If a list, each element should be a cons pair of the form (MAJOR-MODE . LEVEL),
260 where MAJOR-MODE is a symbol or t (meaning the default). For example:
261 ((c-mode . t) (c++-mode . 2) (t . 1))
262 means use the maximum decoration available for buffers in C mode, level 2
263 decoration for buffers in C++ mode, and level 1 decoration otherwise."
280 "If non-nil, means show status messages for buffer fontification.
281 If a number, only buffers greater than this size have fontification messages."
286 \f
288 ;; Originally these variable values were face names such as `bold' etc.
289 ;; Now we create our own faces, but we keep these variables for compatibility
290 ;; and they give users another mechanism for changing face appearance.
291 ;; We now allow a FACENAME in `font-lock-keywords' to be any expression that
292 ;; returns a face. So the easiest thing is to continue using these variables,
293 ;; rather than sometimes evaling FACENAME and sometimes not. sm.
295 ;; Note that in new code, in the vast majority of cases there is no
296 ;; need to create variables that specify face names. Simply using
297 ;; faces directly is enough. Font-lock is not a template to be
298 ;; followed in this area.
333 "Face name to use for easy to overlook negation.
342 ;; Fontification variables:
345 "A list of the keywords to highlight.
346 There are two kinds of values: user-level, and compiled.
348 A user-level keywords list is what a major mode or the user would
349 set up. Normally the list would come from `font-lock-defaults'.
350 through selection of a fontification level and evaluation of any
351 contained expressions. You can also alter it by calling
352 `font-lock-add-keywords' or `font-lock-remove-keywords' with MODE = nil.
354 Each element in a user-level keywords list should have one of these forms:
356 MATCHER
357 (MATCHER . SUBEXP)
358 (MATCHER . FACENAME)
359 (MATCHER . HIGHLIGHT)
360 (MATCHER HIGHLIGHT ...)
361 (eval . FORM)
363 where MATCHER can be either the regexp to search for, or the function name to
364 call to make the search (called with one argument, the limit of the search;
365 it should return non-nil, move point, and set `match-data' appropriately if
366 it succeeds; like `re-search-forward' would).
367 MATCHER regexps can be generated via the function `regexp-opt'.
369 FORM is an expression, whose value should be a keyword element, evaluated when
370 the keyword is (first) used in a buffer. This feature can be used to provide a
371 keyword that can only be generated when Font Lock mode is actually turned on.
373 HIGHLIGHT should be either MATCH-HIGHLIGHT or MATCH-ANCHORED.
376 typically only MATCH-HIGHLIGHT is required.
377 However, if an item or (typically) items are to be highlighted following the
378 instance of another item (the anchor), for example each instance of the
381 MATCH-HIGHLIGHT should be of the form:
383 (SUBEXP FACENAME [OVERRIDE [LAXMATCH]])
385 SUBEXP is the number of the subexpression of MATCHER to be highlighted.
387 FACENAME is an expression whose value is the face name to use.
388 Instead of a face, FACENAME can evaluate to a property list
389 of the form (face FACE PROP1 VAL1 PROP2 VAL2 ...)
390 in which case all the listed text-properties will be set rather than
391 just FACE. In such a case, you will most likely want to put those
392 properties in `font-lock-extra-managed-props' or to override
393 `font-lock-unfontify-region-function'.
395 OVERRIDE and LAXMATCH are flags. If OVERRIDE is t, existing fontification can
396 be overwritten. If `keep', only parts not already fontified are highlighted.
397 If `prepend' or `append', existing fontification is merged with the new, in
398 which the new or existing fontification, respectively, takes precedence.
399 If LAXMATCH is non-nil, that means don't signal an error if there is
400 no match for SUBEXP in MATCHER.
402 For example, an element of the form highlights (if not already highlighted):
405 variable `font-lock-keyword-face'.
407 the value of `font-lock-keyword-face'.
411 of `foo-bar-face', even if already highlighted.
412 (fubar-match 1 fubar-face)
413 the first subexpression within all occurrences of
414 whatever the function `fubar-match' finds and matches
415 in the value of `fubar-face'.
417 MATCH-ANCHORED should be of the form:
419 (MATCHER PRE-MATCH-FORM POST-MATCH-FORM MATCH-HIGHLIGHT ...)
421 where MATCHER is a regexp to search for or the function name to call to make
422 the search, as for MATCH-HIGHLIGHT above, but with one exception; see below.
423 PRE-MATCH-FORM and POST-MATCH-FORM are evaluated before the first, and after
424 the last, instance MATCH-ANCHORED's MATCHER is used. Therefore they can be
425 used to initialize before, and cleanup after, MATCHER is used. Typically,
426 PRE-MATCH-FORM is used to move to some position relative to the original
427 MATCHER, before starting with MATCH-ANCHORED's MATCHER. POST-MATCH-FORM might
428 be used to move back, before resuming with MATCH-ANCHORED's parent's MATCHER.
430 For example, an element of the form highlights (if not already highlighted):
441 The above-mentioned exception is as follows. The limit of the MATCHER search
442 defaults to the end of the line after PRE-MATCH-FORM is evaluated.
443 However, if PRE-MATCH-FORM returns a position greater than the position after
444 PRE-MATCH-FORM is evaluated, that position is used as the limit of the search.
445 It is generally a bad idea to return a position greater than the end of the
446 line, i.e., cause the MATCHER search to span lines.
448 These regular expressions can match text which spans lines, although
449 it is better to avoid it if possible since updating them while editing
450 text is slower, and it is not guaranteed to be always correct when using
451 support modes like jit-lock or lazy-lock.
453 This variable is set by major modes via the variable `font-lock-defaults'.
454 Be careful when composing regexps for this list; a poorly written pattern can
455 dramatically slow things down!
457 A compiled keywords list starts with t. It is produced internal
458 by `font-lock-compile-keywords' from a user-level keywords list.
459 Its second element is the user-level keywords list that was
460 compiled. The remaining elements have the same form as
461 user-level keywords, but normally their values have been
465 "Alist of additional `font-lock-keywords' elements for major modes.
467 Each element has the form (MODE KEYWORDS . HOW).
468 `font-lock-set-defaults' adds the elements in the list KEYWORDS to
469 `font-lock-keywords' when Font Lock is turned on in major mode MODE.
471 If HOW is nil, KEYWORDS are added at the beginning of
472 `font-lock-keywords'. If it is `set', they are used to replace the
473 value of `font-lock-keywords'. If HOW is any other non-nil value,
474 they are added at the end.
476 This is normally set via `font-lock-add-keywords' and
481 "Alist of `font-lock-keywords' elements to be removed for major modes.
483 Each element has the form (MODE . KEYWORDS). `font-lock-set-defaults'
484 removes the elements in the list KEYWORDS from `font-lock-keywords'
485 when Font Lock is turned on in major mode MODE.
487 This is normally set via `font-lock-add-keywords' and
491 "*Non-nil means Font Lock should not fontify comments or strings.
495 "*Non-nil means the patterns in `font-lock-keywords' are case-insensitive.
496 This is set via the function `font-lock-set-defaults', based on
501 "Point up to which `font-lock-syntactic-keywords' has been applied.
502 If nil, this is ignored, in which case the syntactic fontification may
509 "Function to determine which face to use when fontifying syntactically.
510 The function is called with a single parameter (the state as returned by
511 `parse-partial-sexp' at the beginning of the region to highlight) and
515 "A list of the syntactic keywords to put syntax properties on.
516 The value can be the list itself, or the name of a function or variable
517 whose value is the list.
519 See `font-lock-keywords' for a description of the form of this list;
520 only the differences are stated here. MATCH-HIGHLIGHT should be of the form:
522 (SUBEXP SYNTAX OVERRIDE LAXMATCH)
524 where SYNTAX can be a string (as taken by `modify-syntax-entry'), a syntax
525 table, a cons cell (as returned by `string-to-syntax') or an expression whose
526 value is such a form. OVERRIDE cannot be `prepend' or `append'.
528 Here are two examples of elements of `font-lock-syntactic-keywords'
529 and what they do:
534 dollar-sign character. Hash characters in other contexts will still
535 follow whatever the syntax table says about the hash character.
541 gives a pair single-quotes, which surround a single character, a SYNTAX of
543 contexts will not be affected.
550 "Non-nil means use this syntax table for fontifying.
551 If this is nil, the major mode's syntax table is used.
555 "*Non-nil means use this function to move back outside all constructs.
556 When called with no args it should move point backward to a place which
557 is not in a string or comment and not within any bracket-pairs (or else,
558 a place such that any bracket-pairs outside it can be ignored for Emacs
559 syntax analysis and fontification).
561 If this is nil, Font Lock uses `syntax-begin-function' to move back
562 outside of any comment, string, or sexp. This variable is semi-obsolete;
563 we recommend setting `syntax-begin-function' instead.
570 "*Non-nil means use this function to mark a block of text.
571 When called with no args it should leave point at the beginning of any
572 enclosing textual block and mark at the end.
576 "Function to use for fontifying the buffer.
580 "Function to use for unfontifying the buffer.
581 This is used when turning off Font Lock mode.
585 "Function to use for fontifying a region.
586 It should take two args, the beginning and end of the region, and an optional
587 third arg VERBOSE. If VERBOSE is non-nil, the function should print status
591 "Function to use for unfontifying a region.
592 It should take two args, the beginning and end of the region.
596 "List of Font Lock mode related modes that should not be turned on.
597 Currently, valid mode names are `fast-lock-mode', `jit-lock-mode' and
601 "Whether font-lock should cater to multiline keywords.
602 If nil, don't try to handle multiline patterns.
603 If t, always handle multiline patterns.
604 If `undecided', don't try to handle multiline patterns until you see one.
608 \f
609 ;; Font Lock mode.
612 ;;
613 ;; We don't do this at the top-level as we only use non-autoloaded macros.
615 ;;
616 ;; Borrowed from lazy-lock.el.
617 ;; We use this to preserve or protect things when modifying text properties.
619 "Bind variables according to VARLIST and eval BODY restoring buffer state."
624 ;;
625 ;; Shut up the byte compiler.
629 ;; Turn on Font Lock mode.
634 ;; Fontify the buffer if we have to.
637 nil)
643 ;; Turn off Font Lock mode.
650 "Add highlighting KEYWORDS for MODE.
652 MODE should be a symbol, the major mode command name, such as `c-mode'
653 or nil. If nil, highlighting keywords are added for the current buffer.
654 KEYWORDS should be a list; see the variable `font-lock-keywords'.
655 By default they are added at the beginning of the current highlighting list.
656 If optional argument HOW is `set', they are used to replace the current
657 highlighting list. If HOW is any other non-nil value, they are added at the
658 end of the current highlighting list.
660 For example:
662 (font-lock-add-keywords 'c-mode
666 adds two fontification patterns for C mode, to fontify `FIXME:' words, even in
667 comments, and to fontify `and', `or' and `not' words as keywords.
669 The above procedure will only add the keywords for C mode, not
670 for modes derived from C mode. To add them for derived modes too,
671 pass nil for MODE and add the call to c-mode-hook.
673 For example:
675 (add-hook 'c-mode-hook
676 (lambda ()
677 (font-lock-add-keywords nil
680 font-lock-keyword-face)))))
682 The above procedure may fail to add keywords to derived modes if
683 some involved major mode does not follow the standard conventions.
684 File a bug report if this happens, so the major mode can be corrected.
686 Note that some modes have specialized support for additional patterns, e.g.,
687 see the variables `c-font-lock-extra-types', `c++-font-lock-extra-types',
688 `objc-font-lock-extra-types' and `java-font-lock-extra-types'."
690 ;; If MODE is non-nil, add the KEYWORDS and HOW spec to
691 ;; `font-lock-keywords-alist' so `font-lock-set-defaults' uses them.
698 ;; Make sure that `font-lock-removed-keywords-alist' does not
699 ;; contain the new keywords.
704 ;; The major mode has not set any keywords, so when we enabled
705 ;; font-lock-mode it only enabled the font-core.el part, not the
706 ;; font-lock-mode-internal. Try again.
710 ;; Otherwise set or add the keywords now.
711 ;; This is a no-op if it has been done already in this buffer
712 ;; for the correct major mode.
715 ;; Bring back the user-level (uncompiled) keywords.
718 ;; Now modify or replace them.
724 font-lock-keywords)))
728 ;; If the keywords were compiled before, compile them again.
734 "Update `font-lock-removed-keywords-alist' when adding new KEYWORDS to MODE."
735 ;; When font-lock is enabled first all keywords in the list
736 ;; `font-lock-keywords-alist' are added, then all keywords in the
737 ;; list `font-lock-removed-keywords-alist' are removed. If a
738 ;; keyword was once added, removed, and then added again it must be
739 ;; removed from the removed-keywords list. Otherwise the second add
740 ;; will not take effect.
744 ;; A new set of keywords is defined. Forget all about
745 ;; our old keywords that should be removed.
748 ;; Delete all previously removed keywords.
751 ;; Delete the mode cell if empty.
756 ;; Written by Anders Lindgren <andersl@andersl.com>.
757 ;;
758 ;; Case study:
759 ;; (I) The keywords are removed from a major mode.
760 ;; In this case the keyword could be local (i.e. added earlier by
761 ;; `font-lock-add-keywords'), global, or both.
762 ;;
763 ;; (a) In the local case we remove the keywords from the variable
764 ;; `font-lock-keywords-alist'.
765 ;;
766 ;; (b) The actual global keywords are not known at this time.
767 ;; All keywords are added to `font-lock-removed-keywords-alist',
768 ;; when font-lock is enabled those keywords are removed.
769 ;;
770 ;; Note that added keywords are taken out of the list of removed
771 ;; keywords. This ensure correct operation when the same keyword
772 ;; is added and removed several times.
773 ;;
774 ;; (II) The keywords are removed from the current buffer.
776 "Remove highlighting KEYWORDS for MODE.
778 MODE should be a symbol, the major mode command name, such as `c-mode'
779 or nil. If nil, highlighting keywords are removed for the current buffer.
781 To make the removal apply to modes derived from MODE as well,
782 pass nil for MODE and add the call to MODE-hook. This may fail
783 for some derived modes if some involved major mode does not
784 follow the standard conventions. File a bug report if this
785 happens, so the major mode can be corrected."
787 ;; Remove one keyword at the time.
790 ;; If MODE is non-nil, remove the KEYWORD from
791 ;; `font-lock-keywords-alist'.
794 ;; `keywords-list-how-pair' is a cons with a list of
795 ;; keywords in the car top-cell and the original how
796 ;; argument in the cdr top-cell.
799 ;; Remove keyword list/how pair when the keyword list
800 ;; is empty and how doesn't specify `set'. (If it
801 ;; should be deleted then previously deleted keywords
802 ;; would appear again.)
809 ;; Final cleanup, remove major mode cell if last keyword
810 ;; was deleted.
814 ;; Remember the keyword in case it is not local.
820 font-lock-removed-keywords-alist))))))
822 ;; Otherwise remove it immediately.
825 ;; Bring back the user-level (uncompiled) keywords.
829 ;; Edit them.
835 ;; If the keywords were compiled before, compile them again.
839 \f
840 ;;; Font Lock Support mode.
842 ;; This is the code used to interface font-lock.el with any of its add-on
843 ;; packages, and provide the user interface. Packages that have their own
844 ;; local buffer fontification functions (see below) may have to call
845 ;; `font-lock-after-fontify-buffer' and/or `font-lock-after-unfontify-buffer'
846 ;; themselves.
849 "Support mode for Font Lock mode.
850 Support modes speed up Font Lock mode by being choosy about when fontification
851 occurs. The default support mode, Just-in-time Lock mode (symbol
852 `jit-lock-mode'), is recommended.
854 Other, older support modes are Fast Lock mode (symbol `fast-lock-mode') and
855 Lazy Lock mode (symbol `lazy-lock-mode'). See those modes for more info.
856 However, they are no longer recommended, as Just-in-time Lock mode is better.
858 If nil, means support for Font Lock mode is never performed.
859 If a symbol, use that support mode.
860 If a list, each element should be of the form (MAJOR-MODE . SUPPORT-MODE),
861 where MAJOR-MODE is a symbol or t (meaning the default). For example:
862 ((c-mode . fast-lock-mode) (c++-mode . fast-lock-mode) (t . lazy-lock-mode))
863 means that Fast Lock mode is used to support Font Lock mode for buffers in C or
864 C++ modes, and Lazy Lock mode is used to support Font Lock mode otherwise.
866 The value of this variable is used when Font Lock mode is turned on."
882 ))
902 ;; Prepare for jit-lock
907 ;; Don't fontify eagerly (and don't abort if the buffer is large).
909 ;; Use jit-lock.
912 ;; Tell jit-lock how we extend the region to refontify.
914 'font-lock-extend-jit-lock-region-after-change
915 nil t))))
922 ;; Reset local vars to the non-jit-lock case.
930 ;; Useless now that jit-lock intercepts font-lock-fontify-buffer. -sm
931 ;; (jit-lock-mode
932 ;; (jit-lock-after-fontify-buffer))
939 ;; Useless as well. It's only called when:
940 ;; - turning off font-lock: it does not matter if we leave spurious
941 ;; `fontified' text props around since jit-lock-mode is also off.
942 ;; - font-lock-default-fontify-buffer fails: this is not run
943 ;; any more anyway. -sm
944 ;;
945 ;; (jit-lock-mode
946 ;; (jit-lock-after-unfontify-buffer))
950 ;;; End of Font Lock Support mode.
951 \f
952 ;;; Fontification functions.
954 ;; Rather than the function, e.g., `font-lock-fontify-region' containing the
955 ;; code to fontify a region, the function runs the function whose name is the
956 ;; value of the variable, e.g., `font-lock-fontify-region-function'. Normally,
957 ;; the value of this variable is, e.g., `font-lock-default-fontify-region'
958 ;; which does contain the code to fontify a region. However, the value of the
959 ;; variable could be anything and thus, e.g., `font-lock-fontify-region' could
960 ;; do anything. The indirection of the fontification functions gives major
961 ;; modes the capability of modifying the way font-lock.el fontifies. Major
962 ;; modes can modify the values of, e.g., `font-lock-fontify-region-function',
963 ;; via the variable `font-lock-defaults'.
964 ;;
965 ;; For example, Rmail mode sets the variable `font-lock-defaults' so that
966 ;; font-lock.el uses its own function for buffer fontification. This function
967 ;; makes fontification be on a message-by-message basis and so visiting an
968 ;; RMAIL file is much faster. A clever implementation of the function might
969 ;; fontify the headers differently than the message body. (It should, and
970 ;; correspondingly for Mail mode, but I can't be bothered to do the work. Can
971 ;; you?) This hints at a more interesting use...
972 ;;
973 ;; Languages that contain text normally contained in different major modes
974 ;; could define their own fontification functions that treat text differently
975 ;; depending on its context. For example, Perl mode could arrange that here
976 ;; docs are fontified differently than Perl code. Or Yacc mode could fontify
977 ;; rules one way and C code another. Neat!
978 ;;
979 ;; A further reason to use the fontification indirection feature is when the
980 ;; default syntactual fontification, or the default fontification in general,
981 ;; is not flexible enough for a particular major mode. For example, perhaps
982 ;; comments are just too hairy for `font-lock-fontify-syntactically-region' to
983 ;; cope with. You need to write your own version of that function, e.g.,
984 ;; `hairy-fontify-syntactically-region', and make your own version of
985 ;; `hairy-fontify-region' call that function before calling
986 ;; `font-lock-fontify-keywords-region' for the normal regexp fontification
987 ;; pass. And Hairy mode would set `font-lock-defaults' so that font-lock.el
988 ;; would call your region fontification function instead of its own. For
989 ;; example, TeX modes could fontify {\foo ...} and \bar{...} etc. multi-line
990 ;; directives correctly and cleanly. (It is the same problem as fontifying
991 ;; multi-line strings and comments; regexps are not appropriate for the job.)
994 "A function that determines the region to refontify after a change.
996 This variable is either nil, or is a function that determines the
997 region to refontify after a change.
998 It is usually set by the major mode via `font-lock-defaults'.
999 Font-lock calls this function after each buffer change.
1001 The function is given three parameters, the standard BEG, END, and OLD-LEN
1002 from `after-change-functions'. It should return either a cons of the beginning
1003 and end buffer positions \(in that order) of the region to refontify, or nil
1004 \(which directs the caller to fontify a default region).
1005 This function should preserve the match-data.
1010 "Fontify the current buffer the way the function `font-lock-mode' would."
1031 font-lock-verbose)))
1035 ;; Make sure we fontify etc. in the whole buffer.
1044 ;; We don't restore the old fontification, so it's best to unfontify.
1048 ;; Make sure we unfontify etc. in the whole buffer.
1056 "If non-nil, font-lock will work on the non-widened buffer.
1057 Useful for things like RMAIL and Info where the whole buffer is not
1064 ;; This use of font-lock-multiline property is unreliable but is just
1065 ;; a handy heuristic: in case you don't have a function that does
1066 ;; /identification/ of multiline elements, you may still occasionally
1067 ;; discover them by accident (or you may /identify/ them but not in all
1068 ;; cases), in which case the font-lock-multiline property can help make
1069 ;; sure you will properly *re*identify them during refontification.
1070 font-lock-extend-region-multiline)
1071 "Special hook run just before proceeding to fontify a region.
1072 This is used to allow major modes to help font-lock find safe buffer positions
1073 as beginning and end of the fontified region. Its most common use is to solve
1074 the problem of /identification/ of multiline elements by providing a function
1075 that tries to find such elements and move the boundaries such that they do
1076 not fall in the middle of one.
1077 Each function is called with no argument; it is expected to adjust the
1078 dynamically bound variables `font-lock-beg' and `font-lock-end'; and return
1079 non-nil if it did make such an adjustment.
1080 These functions are run in turn repeatedly until they all return nil.
1082 ;; Mark it as a special hook which doesn't use any global setting
1083 ;; (i.e. doesn't obey the element t in the buffer-local value).
1087 "Move fontification boundaries away from any `font-lock-multiline' property."
1095 ;;
1101 changed))
1104 "Move fontification boundaries to beginning of lines."
1114 changed))
1118 ;; Use the fontification syntax table, if any.
1122 ;; Extend the region to fontify so that it starts and ends at
1123 ;; safe places.
1131 ;; If there's been a change, we should go through
1132 ;; the list again since this new position may
1133 ;; warrant a different answer from one of the fun
1134 ;; we've already seen.
1135 font-lock-extend-region-functions)))
1137 ;; Now do the fontification.
1141 ;; Ensure the beginning of the file is properly syntactic-fontified.
1151 ;; The following must be rethought, since keywords can override fontification.
1152 ;; ;; Now scan for keywords, but not if we are inside a comment now.
1153 ;; (or (and (not font-lock-keywords-only)
1154 ;; (let ((state (parse-partial-sexp beg end nil nil
1155 ;; font-lock-cache-state)))
1156 ;; (or (nth 4 state) (nth 7 state))))
1157 ;; (font-lock-fontify-keywords-region beg end))
1160 "Additional text properties managed by font-lock.
1161 This is used by `font-lock-default-unfontify-region' to decide
1167 font-lock-extra-managed-props
1172 ;; Called when any modification is made to buffer text.
1179 beg end old-len))))
1182 ;; Fontify the region the major mode has specified.
1184 ;; Fontify the whole lines which enclose the region.
1185 ;; Actually, this is not needed because
1186 ;; font-lock-default-fontify-region already rounds up to a whole
1187 ;; number of lines.
1188 ;; (setq beg (progn (goto-char beg) (line-beginning-position))
1189 ;; end (progn (goto-char end) (line-beginning-position 2)))
1191 ;; Rounding up to a whole number of lines should include the
1192 ;; line right after `end'. Typical case: the first char of
1193 ;; the line was deleted. Or a \n was inserted in the middle
1194 ;; of a line.
1200 "Function meant for `jit-lock-after-change-extend-region-functions'.
1201 This function does 2 things:
1202 - extend the region so that it not only includes the part that was modified
1203 but also the surrounding text whose highlighting may change as a consequence.
1204 - anticipate (part of) the region extension that will happen later in
1205 `font-lock-default-fontify-region', in order to avoid the need for
1206 double-redisplay in `jit-lock-fontify-now'."
1208 ;; First extend the region as font-lock-after-change-function would.
1211 beg end old-len))))
1215 ;; Then extend the region obeying font-lock-multiline properties,
1216 ;; indicating which part of the buffer needs to be refontified.
1217 ;; !!! This is the *main* user of font-lock-multiline property !!!
1218 ;; font-lock-after-change-function could/should also do that, but it
1219 ;; doesn't need to because font-lock-default-fontify-region does
1220 ;; it anyway. Here OTOH we have no guarantee that
1221 ;; font-lock-default-fontify-region will be executed on this region
1222 ;; any time soon.
1223 ;; Note: contrary to font-lock-default-fontify-region, we do not do
1224 ;; any loop here because we are not looking for a safe spot: we just
1225 ;; mark the text whose appearance may need to change as a result of
1226 ;; the buffer modification.
1238 ;; Rounding up to a whole number of lines should include the
1239 ;; line right after `end'. Typical case: the first char of
1240 ;; the line was deleted. Or a \n was inserted in the middle
1241 ;; of a line.
1243 ;; Finally, pre-enlarge the region to a whole number of lines, to try
1244 ;; and anticipate what font-lock-default-fontify-region will do, so as to
1245 ;; avoid double-redisplay.
1246 ;; We could just run `font-lock-extend-region-functions', but since
1247 ;; the only purpose is to avoid the double-redisplay, we prefer to
1248 ;; do here only the part that is cheap and most likely to be useful.
1250 font-lock-extend-region-functions)
1259 "Fontify some lines the way `font-lock-fontify-buffer' would.
1260 The lines could be a function or paragraph, or a specified number of lines.
1261 If ARG is given, fontify that many lines before and after point, or 16 lines if
1262 no ARG is given and `font-lock-mark-block-function' is nil.
1263 If `font-lock-mark-block-function' non-nil and no ARG is given, it is used to
1264 delimit the region to fontify."
1267 deactivate-mark)
1268 ;; Make sure we have the right `font-lock-keywords' etc.
1282 ;;; End of Fontification functions.
1283 \f
1284 ;;; Additional text property functions.
1286 ;; The following text property functions should be builtins. This means they
1287 ;; should be written in C and put with all the other text property functions.
1288 ;; In the meantime, those that are used by font-lock.el are defined in Lisp
1289 ;; below and given a `font-lock-' prefix. Those that are not used are defined
1290 ;; in Lisp below and commented out. sm.
1293 "Prepend to one property of the text from START to END.
1294 Arguments PROP and VALUE specify the property and value to prepend to the value
1295 already in place. The resulting property values are always lists.
1296 Optional argument OBJECT is the string or buffer containing the text."
1301 ;; Canonicalize old forms of face property.
1309 object)
1313 "Append to one property of the text from START to END.
1314 Arguments PROP and VALUE specify the property and value to append to the value
1315 already in place. The resulting property values are always lists.
1316 Optional argument OBJECT is the string or buffer containing the text."
1321 ;; Canonicalize old forms of face property.
1329 object)
1333 "Fill in one property of the text from START to END.
1334 Arguments PROP and VALUE specify the property and value to put where none are
1335 already in place. Therefore existing property values are not overwritten.
1336 Optional argument OBJECT is the string or buffer containing the text."
1343 ;; For completeness: this is to `remove-text-properties' as `put-text-property'
1344 ;; is to `add-text-properties', etc.
1345 ;;(defun remove-text-property (start end property &optional object)
1346 ;; "Remove a property from text from START to END.
1347 ;;Argument PROPERTY is the property to remove.
1348 ;;Optional argument OBJECT is the string or buffer containing the text.
1349 ;;Return t if the property was actually removed, nil otherwise."
1350 ;; (remove-text-properties start end (list property) object))
1352 ;; For consistency: maybe this should be called `remove-single-property' like
1353 ;; `next-single-property-change' (not `next-single-text-property-change'), etc.
1354 ;;(defun remove-single-text-property (start end prop value &optional object)
1355 ;; "Remove a specific property value from text from START to END.
1356 ;;Arguments PROP and VALUE specify the property and value to remove. The
1357 ;;resulting property values are not equal to VALUE nor lists containing VALUE.
1358 ;;Optional argument OBJECT is the string or buffer containing the text."
1359 ;; (let ((start (text-property-not-all start end prop nil object)) next prev)
1360 ;; (while start
1361 ;; (setq next (next-single-property-change start prop object end)
1362 ;; prev (get-text-property start prop object))
1363 ;; (cond ((and (symbolp prev) (eq value prev))
1364 ;; (remove-text-property start next prop object))
1365 ;; ((and (listp prev) (memq value prev))
1366 ;; (let ((new (delq value prev)))
1367 ;; (cond ((null new)
1368 ;; (remove-text-property start next prop object))
1369 ;; ((= (length new) 1)
1370 ;; (put-text-property start next prop (car new) object))
1371 ;; (t
1372 ;; (put-text-property start next prop new object))))))
1373 ;; (setq start (text-property-not-all next end prop nil object)))))
1375 ;;; End of Additional text property functions.
1376 \f
1377 ;;; Syntactic regexp fontification functions.
1379 ;; These syntactic keyword pass functions are identical to those keyword pass
1380 ;; functions below, with the following exceptions; (a) they operate on
1381 ;; `font-lock-syntactic-keywords' of course, (b) they are all `defun' as speed
1382 ;; is less of an issue, (c) eval of property value does not occur JIT as speed
1383 ;; is less of an issue, (d) OVERRIDE cannot be `prepend' or `append' as it
1384 ;; makes no sense for `syntax-table' property values, (e) they do not do it
1385 ;; LOUDLY as it is not likely to be intensive.
1388 "Apply HIGHLIGHT following a match.
1389 HIGHLIGHT should be of the form MATCH-HIGHLIGHT,
1390 see `font-lock-syntactic-keywords'."
1396 ;; No match but we might not signal an error.
1402 ;; Flush the syntax-cache. I believe this is not necessary for
1403 ;; font-lock's use of syntax-ppss, but I'm not 100% sure and it can
1404 ;; still be necessary for other users of syntax-ppss anyway.
1408 ;; Cannot override existing fontification.
1412 ;; Override existing fontification.
1415 ;; Keep existing fontification.
1419 "Fontify according to KEYWORDS until LIMIT.
1420 KEYWORDS should be of the form MATCH-ANCHORED, see `font-lock-keywords',
1421 LIMIT can be modified by the value of its PRE-MATCH-FORM."
1423 ;; Evaluate PRE-MATCH-FORM.
1425 ;; Set LIMIT to value of PRE-MATCH-FORM or the end of line.
1430 ;; Find an occurrence of `matcher' before `limit'.
1434 ;; Apply each highlight to this instance of `matcher'.
1439 ;; Evaluate POST-MATCH-FORM.
1443 "Fontify according to `font-lock-syntactic-keywords' between START and END.
1444 START should be at the beginning of a line."
1446 ;; We wouldn't go through so much trouble if we didn't intend to use those
1447 ;; properties, would we?
1449 ;; If `font-lock-syntactic-keywords' is a symbol, get the real keywords.
1452 font-lock-syntactic-keywords)))
1453 ;; If `font-lock-syntactic-keywords' is not compiled, compile it.
1456 font-lock-syntactic-keywords
1457 t)))
1458 ;; Get down to business.
1461 keyword matcher highlights)
1463 ;; Find an occurrence of `matcher' from `start' to `end'.
1470 ;; Apply each highlight to this instance of `matcher', which may be
1471 ;; specific highlights or more keywords anchored to `matcher'.
1477 end))
1481 ;;; End of Syntactic regexp fontification functions.
1482 \f
1483 ;;; Syntactic fontification functions.
1492 "Put proper face on each string and comment between START and END.
1493 START should be at the beginning of a line."
1499 ;; Find the `start' state.
1501 face beg)
1503 ;;
1504 ;; Find each interesting place between here and `end'.
1515 comment-start-skip))
1516 ;; Find the comment delimiters
1517 ;; and use font-lock-comment-delimiter-face for them.
1521 comment-start-skip))
1523 font-lock-comment-delimiter-face)))
1526 font-lock-comment-delimiter-face))))
1531 ;;; End of Syntactic fontification functions.
1532 \f
1533 ;;; Keyword regexp fontification functions.
1536 "Apply HIGHLIGHT following a match.
1537 HIGHLIGHT should be of the form MATCH-HIGHLIGHT, see `font-lock-keywords'."
1542 ;; No match but we might not signal an error.
1551 ;; If `val' is nil, don't do anything. It is important to do it
1552 ;; explicitly, because when adding nil via things like
1553 ;; font-lock-append-text-property, the property is actually
1554 ;; changed from <face> to (<face>) which is undesirable. --Stef
1555 nil)
1557 ;; Cannot override existing fontification.
1561 ;; Override existing fontification.
1564 ;; Prepend to existing fontification.
1567 ;; Append to existing fontification.
1570 ;; Keep existing fontification.
1574 "Fontify according to KEYWORDS until LIMIT.
1575 KEYWORDS should be of the form MATCH-ANCHORED, see `font-lock-keywords',
1576 LIMIT can be modified by the value of its PRE-MATCH-FORM."
1579 ;; Evaluate PRE-MATCH-FORM.
1581 ;; Set LIMIT to value of PRE-MATCH-FORM or the end of line.
1586 ;; this is a multiline anchored match
1587 ;; (setq font-lock-multiline t)
1591 limit
1594 ;; Find an occurrence of `matcher' before `limit'.
1599 ;; Apply each highlight to this instance of `matcher'.
1604 ;; Evaluate POST-MATCH-FORM.
1608 "Fontify according to `font-lock-keywords' between START and END.
1609 START should be at the beginning of a line.
1610 LOUDLY, if non-nil, allows progress-meter bar."
1618 keyword matcher highlights)
1619 ;;
1620 ;; Fontify each item in `font-lock-keywords' from `start' to `end'.
1624 ;;
1625 ;; Find an occurrence of `matcher' from `start' to `end'.
1632 ;; Beware empty string matches since they will
1633 ;; loop indefinitely.
1640 ;; this is a multiline regexp match
1641 ;; (setq font-lock-multiline t)
1650 ;; Apply each highlight to this instance of `matcher', which may be
1651 ;; specific highlights or more keywords anchored to `matcher'.
1658 ;; Ensure forward progress. `pos' is a marker because anchored
1659 ;; keyword may add/delete text (this happens e.g. in grep.el).
1665 ;;; End of Keyword regexp fontification functions.
1666 \f
1667 ;; Various functions.
1670 "Compile KEYWORDS into the form (t KEYWORDS COMPILED...)
1671 Here each COMPILED is of the form (MATCHER HIGHLIGHT ...) as shown in the
1672 `font-lock-keywords' doc string.
1673 If SYNTACTIC-KEYWORDS is non-nil, it means these keywords are used for
1674 `font-lock-syntactic-keywords' rather than for `font-lock-keywords'."
1676 ;; This should never happen. But some external packages sometimes
1677 ;; call font-lock in unexpected and incorrect ways. It's important to
1678 ;; stop processing at this point, otherwise we may end up changing the
1679 ;; global value of font-lock-keywords and break highlighting in many
1680 ;; other buffers.
1683 keywords
1690 syntax-begin-function)))
1694 ;; Try to detect when a string or comment contains something that
1695 ;; looks like a defun and would thus confuse font-lock.
1703 font-lock-comment-face))
1706 prepend)))))
1707 keywords))
1715 ;; If FORM is a FACENAME then quote it. Otherwise ignore the quote.
1726 keyword)))
1729 "Evalulate KEYWORDS if a function (funcall) or variable (eval) name."
1731 keywords
1737 "Return value in ALIST for `major-mode', or ALIST if it is not an alist.
1738 Structure is ((MAJOR-MODE . VALUE) ...) where MAJOR-MODE may be t."
1741 alist))
1744 "Return LEVELth element of KEYWORDS.
1745 A LEVEL of nil is equal to a LEVEL of 0, a LEVEL of t is equal to
1746 \(1- (length KEYWORDS))."
1748 keywords)
1759 "Restart fontification in current buffer after recomputing from defaults.
1760 Recompute fontification variables using `font-lock-defaults' and
1761 `font-lock-maximum-decoration'. Then restart fontification.
1763 Use this function when you have changed any of the above
1764 variables directly.
1766 Note: This function will erase modifications done by
1767 `font-lock-add-keywords' or `font-lock-remove-keywords', but will
1768 preserve `hi-lock-mode' highlighting patterns."
1779 "Set fontification defaults appropriately for this mode.
1780 Sets various variables using `font-lock-defaults' and
1781 `font-lock-maximum-decoration'."
1782 ;; Set fontification defaults if not previously set for correct major mode.
1797 ;; Syntactic fontification?
1801 ;; Case fold during regexp fontification?
1805 ;; Syntax table for regexp and syntactic fontification?
1811 ;; The character to modify may be a single CHAR or a STRING.
1817 ;; Syntax function for syntactic fontification?
1822 ;; Variable alist?
1825 ;; Set up `font-lock-keywords' last because its value might depend
1826 ;; on other settings (e.g. font-lock-compile-keywords uses
1827 ;; font-lock-beginning-of-syntax-function).
1830 ;; Local fontification?
1836 ;; Now compile the keywords.
1840 \f
1841 ;;; Color etc. support.
1843 ;; Note that `defface' will not overwrite any faces declared above via
1844 ;; `custom-declare-face'.
1861 )
1863 "Font Lock mode face used to highlight comments."
1874 "Font Lock mode face used to highlight comment delimiters."
1886 "Font Lock mode face used to highlight strings."
1891 "Font Lock mode face used to highlight documentation."
1903 "Font Lock mode face used to highlight keywords."
1915 "Font Lock mode face used to highlight builtins."
1925 "Font Lock mode face used to highlight function names."
1939 "Font Lock mode face used to highlight variable names."
1951 "Font Lock mode face used to highlight type and classes."
1965 "Font Lock mode face used to highlight constants and labels."
1975 "Font Lock mode face used to highlight warnings."
1980 "Font Lock mode face used to highlight easy to overlook negation."
1985 "Font Lock mode face used to highlight preprocessor directives."
1990 "Font Lock mode face for backslashes in Lisp regexp grouping constructs."
1995 "Font Lock mode face used to highlight grouping constructs in Lisp regexps."
1998 ;;; End of Color etc. support.
1999 \f
2000 ;;; Menu support.
2002 ;; This section of code is commented out because Emacs does not have real menu
2003 ;; buttons. (We can mimic them by putting "( ) " or "(X) " at the beginning of
2004 ;; the menu entry text, but with Xt it looks both ugly and embarrassingly
2005 ;; amateur.) If/When Emacs gets real menus buttons, put in menu-bar.el after
2006 ;; the entry for "Text Properties" something like:
2007 ;;
2008 ;; (define-key menu-bar-edit-menu [font-lock]
2009 ;; (cons "Syntax Highlighting" font-lock-menu))
2010 ;;
2011 ;; and remove a single ";" from the beginning of each line in the rest of this
2012 ;; section. Probably the mechanism for telling the menu code what are menu
2013 ;; buttons and when they are on or off needs tweaking. I have assumed that the
2014 ;; mechanism is via `menu-toggle' and `menu-selected' symbol properties. sm.
2016 ;;;;;###autoload
2017 ;;(progn
2018 ;; ;; Make the Font Lock menu.
2019 ;; (defvar font-lock-menu (make-sparse-keymap "Syntax Highlighting"))
2020 ;; ;; Add the menu items in reverse order.
2021 ;; (define-key font-lock-menu [fontify-less]
2022 ;; '("Less In Current Buffer" . font-lock-fontify-less))
2023 ;; (define-key font-lock-menu [fontify-more]
2024 ;; '("More In Current Buffer" . font-lock-fontify-more))
2025 ;; (define-key font-lock-menu [font-lock-sep]
2026 ;; '("--"))
2027 ;; (define-key font-lock-menu [font-lock-mode]
2028 ;; '("In Current Buffer" . font-lock-mode))
2029 ;; (define-key font-lock-menu [global-font-lock-mode]
2030 ;; '("In All Buffers" . global-font-lock-mode)))
2031 ;;
2032 ;;;;;###autoload
2033 ;;(progn
2034 ;; ;; We put the appropriate `menu-enable' etc. symbol property values on when
2035 ;; ;; font-lock.el is loaded, so we don't need to autoload the three variables.
2036 ;; (put 'global-font-lock-mode 'menu-toggle t)
2037 ;; (put 'font-lock-mode 'menu-toggle t)
2038 ;; (put 'font-lock-fontify-more 'menu-enable '(identity))
2039 ;; (put 'font-lock-fontify-less 'menu-enable '(identity)))
2040 ;;
2041 ;; ;; Put the appropriate symbol property values on now. See above.
2042 ;;(put 'global-font-lock-mode 'menu-selected 'global-font-lock-mode)
2043 ;;(put 'font-lock-mode 'menu-selected 'font-lock-mode)
2044 ;;(put 'font-lock-fontify-more 'menu-enable '(nth 2 font-lock-fontify-level))
2045 ;;(put 'font-lock-fontify-less 'menu-enable '(nth 1 font-lock-fontify-level))
2046 ;;
2047 ;;(defvar font-lock-fontify-level nil) ; For less/more fontification.
2048 ;;
2049 ;;(defun font-lock-fontify-level (level)
2050 ;; (let ((font-lock-maximum-decoration level))
2051 ;; (when font-lock-mode
2052 ;; (font-lock-mode))
2053 ;; (font-lock-mode)
2054 ;; (when font-lock-verbose
2055 ;; (message "Fontifying %s... level %d" (buffer-name) level))))
2056 ;;
2057 ;;(defun font-lock-fontify-less ()
2058 ;; "Fontify the current buffer with less decoration.
2059 ;;See `font-lock-maximum-decoration'."
2060 ;; (interactive)
2061 ;; ;; Check in case we get called interactively.
2062 ;; (if (nth 1 font-lock-fontify-level)
2063 ;; (font-lock-fontify-level (1- (car font-lock-fontify-level)))
2064 ;; (error "No less decoration")))
2065 ;;
2066 ;;(defun font-lock-fontify-more ()
2067 ;; "Fontify the current buffer with more decoration.
2068 ;;See `font-lock-maximum-decoration'."
2069 ;; (interactive)
2070 ;; ;; Check in case we get called interactively.
2071 ;; (if (nth 2 font-lock-fontify-level)
2072 ;; (font-lock-fontify-level (1+ (car font-lock-fontify-level)))
2073 ;; (error "No more decoration")))
2074 ;;
2075 ;; ;; This should be called by `font-lock-set-defaults'.
2076 ;;(defun font-lock-set-menu ()
2077 ;; ;; Activate less/more fontification entries if there are multiple levels for
2078 ;; ;; the current buffer. Sets `font-lock-fontify-level' to be of the form
2079 ;; ;; (CURRENT-LEVEL IS-LOWER-LEVEL-P IS-HIGHER-LEVEL-P) for menu activation.
2080 ;; (let ((keywords (nth 0 font-lock-defaults))
2081 ;; (level (font-lock-value-in-major-mode font-lock-maximum-decoration)))
2082 ;; (make-local-variable 'font-lock-fontify-level)
2083 ;; (if (or (symbolp keywords) (= (length keywords) 1))
2084 ;; (font-lock-unset-menu)
2085 ;; (cond ((eq level t)
2086 ;; (setq level (1- (length keywords))))
2087 ;; ((or (null level) (zerop level))
2088 ;; ;; The default level is usually, but not necessarily, level 1.
2089 ;; (setq level (- (length keywords)
2090 ;; (length (member (eval (car keywords))
2091 ;; (mapcar 'eval (cdr keywords))))))))
2092 ;; (setq font-lock-fontify-level (list level (> level 1)
2093 ;; (< level (1- (length keywords))))))))
2094 ;;
2095 ;; ;; This should be called by `font-lock-unset-defaults'.
2096 ;;(defun font-lock-unset-menu ()
2097 ;; ;; Deactivate less/more fontification entries.
2098 ;; (setq font-lock-fontify-level nil))
2100 ;;; End of Menu support.
2101 \f
2102 ;;; Various regexp information shared by several modes.
2103 ;; ;; Information specific to a single mode should go in its load library.
2105 ;; Font Lock support for C, C++, Objective-C and Java modes is now in
2106 ;; cc-fonts.el (and required by cc-mode.el). However, the below function
2107 ;; should stay in font-lock.el, since it is used by other libraries. sm.
2110 "Match, and move over, any declaration/definition item after point.
2111 Matches after point, but ignores leading whitespace and `*' characters.
2112 Does not move further than LIMIT.
2114 The expected syntax of a declaration/definition item is `word' (preceded by
2115 optional whitespace and `*' characters and proceeded by optional whitespace)
2116 optionally followed by a `('. Everything following the item (but belonging to
2117 it) is expected to be skip-able by `scan-sexps', and items are expected to be
2118 separated with a `,' and to be terminated with a `;'.
2120 Thus the regexp matches after point: word (
2121 ^^^^ ^
2122 Where the match subexpressions are: 1 2
2124 The item is delimited by (match-beginning 1) and (match-end 1).
2125 If (match-beginning 2) is non-nil, the item is followed by a `('.
2127 This function could be MATCHER in a MATCH-ANCHORED `font-lock-keywords' item."
2130 ;; If `word' is followed by a double open-paren, it's probably
2131 ;; a macro used for "int myfun P_ ((int arg1))". Let's go back one
2132 ;; word to try and match `myfun' rather than `P_'.
2137 ;; Looks like it was something else, so go back to where we
2138 ;; were and reset the match data by rematching.
2144 ;; Restrict to the LIMIT.
2147 ;; Move over any item value, etc., to the next item.
2154 ;; C preprocessor(cpp) is used outside of C, C++ and Objective-C source file.
2155 ;; e.g. assembler code and GNU linker script in Linux kernel.
2156 ;; `cpp-font-lock-keywords' is handy for modes for the files.
2157 ;;
2158 ;; Here we cannot use `regexp-opt' because because regex-opt is not preloaded
2159 ;; while font-lock.el is preloaded to emacs. So values pre-calculated with
2160 ;; regexp-opt are used here.
2162 ;; `cpp-font-lock-keywords-source-directives' is calculated from:
2163 ;;
2164 ;; (regexp-opt
2165 ;; '("define" "elif" "else" "endif" "error" "file" "if" "ifdef"
2166 ;; "ifndef" "import" "include" "line" "pragma" "undef" "warning"))
2167 ;;
2169 "define\\|e\\(?:l\\(?:if\\|se\\)\\|ndif\\|rror\\)\\|file\\|i\\(?:f\\(?:n?def\\)?\\|mport\\|nclude\\)\\|line\\|pragma\\|undef\\|warning"
2172 ;; `cpp-font-lock-keywords-source-depth' is calculated from:
2173 ;;
2174 ;; (regexp-opt-depth (regexp-opt
2175 ;; '("define" "elif" "else" "endif" "error" "file" "if" "ifdef"
2176 ;; "ifndef" "import" "include" "line" "pragma" "undef" "warning")))
2177 ;;
2179 "An integer representing regular expression depth of `cpp-font-lock-keywords-source-directives'.
2186 ;;
2187 ;; Fontify error directives.
2189 ;;
2190 ;; Fontify filenames in #include <...> preprocessor directives as strings.
2193 ;;
2194 ;; Fontify function macro names.
2197 ;;
2198 ;; Macro arguments.
2203 limit)
2204 t))
2206 ;;
2207 ;; Fontify symbol names in #elif or #if ... defined preprocessor directives.
2211 ;;
2212 ;; Fontify otherwise as symbol names, and the preprocessor directive names.
2219 "Font lock keywords for C preprocessor directives.
2220 `c-mode', `c++-mode' and `objc-mode' have their own font lock keywords
2221 for C preprocessor directives. This definition is for the other modes
2222 in which C preprocessor directives are used. e.g. `asm-mode' and
2225 \f
2226 ;; Lisp.
2232 ;; Function declarations.
2239 ;; Variable declarations.
2241 ;; Structure declarations.
2244 ;; Any whitespace and defined object.
2251 nil t))
2252 ;; Emacs Lisp autoload cookies. Supports the slightly different
2253 ;; forms used by mh-e, calendar, etc.
2255 ;; Regexp negated char group.
2276 "with-electric-help"
2285 ;; Control structures. Common Lisp forms.
2306 ;; Exit/Feature symbols as constants.
2311 ;; Erroneous structures.
2312 ("(\\(abort\\|assert\\|warn\\|check-type\\|cerror\\|error\\|signal\\)\\>" 1 font-lock-warning-face)
2313 ;; Words inside \\[] tend to be for `substitute-command-keys'.
2315 ;; Words inside `' tend to be symbol names.
2317 ;; Constant values.
2319 ;; ELisp and CLisp `&' keywords as types.
2321 ;; ELisp regexp grouping constructs
2324 ;; The following loop is needed to continue searching after matches
2325 ;; that do not occur in strings. The associated regexp matches one
2326 ;; of `\\\\' `\\(' `\\(?:' `\\|' `\\)'. `\\\\' has been included to
2327 ;; avoid highlighting, for example, `\\(' in `\\\\('.
2328 (while (re-search-forward "\\(\\\\\\\\\\)\\(?:\\(\\\\\\\\\\)\\|\\((\\(?:\\?[0-9]*:\\)?\\|[|)]\\)\\)" bound t)
2337 ;;; This is too general -- rms.
2338 ;;; A user complained that he has functions whose names start with `do'
2339 ;;; and that they get the wrong color.
2340 ;;; ;; CL `with-' and `do-' constructs
2341 ;;; ("(\\(\\(do-\\|with-\\)\\(\\s_\\|\\w\\)*\\)" 1 font-lock-keyword-face)
2342 )))
2347 \f
2350 ;;; font-lock.el ends here