| blob | 7da2c0f56524bdc616887c3251ed2acb60b7ab7e |
1 ;;; font-lock.el --- Electric font lock mode
3 ;; Copyright (C) 1992-1999 Free Software Foundation, Inc.
5 ;; Author: jwz, then rms, then sm <simon@gnu.org>
6 ;; Maintainer: FSF
7 ;; Keywords: languages, faces
9 ;; This file is part of GNU Emacs.
11 ;; GNU Emacs is free software; you can redistribute it and/or modify
12 ;; it under the terms of the GNU General Public License as published by
13 ;; the Free Software Foundation; either version 2, or (at your option)
14 ;; any later version.
16 ;; GNU Emacs is distributed in the hope that it will be useful,
17 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
18 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
19 ;; GNU General Public License for more details.
21 ;; You should have received a copy of the GNU General Public License
22 ;; along with GNU Emacs; see the file COPYING. If not, write to the
23 ;; Free Software Foundation, Inc., 59 Temple Place - Suite 330,
24 ;; Boston, MA 02111-1307, USA.
26 ;;; Commentary:
28 ;; Font Lock mode is a minor mode that causes your comments to be displayed in
29 ;; one face, strings in another, reserved words in another, and so on.
30 ;;
31 ;; Comments will be displayed in `font-lock-comment-face'.
32 ;; Strings will be displayed in `font-lock-string-face'.
33 ;; Regexps are used to display selected patterns in other faces.
34 ;;
35 ;; To make the text you type be fontified, use M-x font-lock-mode RET.
36 ;; When this minor mode is on, the faces of the current line are updated with
37 ;; every insertion or deletion.
38 ;;
39 ;; To turn Font Lock mode on automatically, add this to your ~/.emacs file:
40 ;;
41 ;; (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
42 ;;
43 ;; Or if you want to turn Font Lock mode on in many modes:
44 ;;
45 ;; (global-font-lock-mode t)
46 ;;
47 ;; Fontification for a particular mode may be available in a number of levels
48 ;; of decoration. The higher the level, the more decoration, but the more time
49 ;; it takes to fontify. See the variable `font-lock-maximum-decoration', and
50 ;; also the variable `font-lock-maximum-size'. Support modes for Font Lock
51 ;; mode can be used to speed up Font Lock mode. See `font-lock-support-mode'.
52 \f
53 ;;; How Font Lock mode fontifies:
55 ;; When Font Lock mode is turned on in a buffer, it (a) fontifies the entire
56 ;; buffer and (b) installs one of its fontification functions on one of the
57 ;; hook variables that are run by Emacs after every buffer change (i.e., an
58 ;; insertion or deletion). Fontification means the replacement of `face' text
59 ;; properties in a given region; Emacs displays text with these `face' text
60 ;; properties appropriately.
61 ;;
62 ;; Fontification normally involves syntactic (i.e., strings and comments) and
63 ;; regexp (i.e., keywords and everything else) passes. There are actually
64 ;; three passes; (a) the syntactic keyword pass, (b) the syntactic pass and (c)
65 ;; the keyword pass. Confused?
66 ;;
67 ;; The syntactic keyword pass places `syntax-table' text properties in the
68 ;; buffer according to the variable `font-lock-syntactic-keywords'. It is
69 ;; necessary because Emacs' syntax table is not powerful enough to describe all
70 ;; the different syntactic constructs required by the sort of people who decide
71 ;; that a single quote can be syntactic or not depending on the time of day.
72 ;; (What sort of person could decide to overload the meaning of a quote?)
73 ;; Obviously the syntactic keyword pass must occur before the syntactic pass.
74 ;;
75 ;; The syntactic pass places `face' text properties in the buffer according to
76 ;; syntactic context, i.e., according to the buffer's syntax table and buffer
77 ;; text's `syntax-table' text properties. It involves using a syntax parsing
78 ;; function to determine the context of different parts of a region of text. A
79 ;; syntax parsing function is necessary because generally strings and/or
80 ;; comments can span lines, and so the context of a given region is not
81 ;; necessarily apparent from the content of that region. Because the keyword
82 ;; pass only works within a given region, it is not generally appropriate for
83 ;; syntactic fontification. This is the first fontification pass that makes
84 ;; changes visible to the user; it fontifies strings and comments.
85 ;;
86 ;; The keyword pass places `face' text properties in the buffer according to
87 ;; the variable `font-lock-keywords'. It involves searching for given regexps
88 ;; (or calling given search functions) within the given region. This is the
89 ;; second fontification pass that makes changes visible to the user; it
90 ;; fontifies language reserved words, etc.
91 ;;
92 ;; Oh, and the answer is, "Yes, obviously just about everything should be done
93 ;; in a single syntactic pass, but the only syntactic parser available
94 ;; understands only strings and comments." Perhaps one day someone will write
95 ;; some syntactic parsers for common languages and a son-of-font-lock.el could
96 ;; use them rather then relying so heavily on the keyword (regexp) pass.
98 ;;; How Font Lock mode supports modes or is supported by modes:
100 ;; Modes that support Font Lock mode do so by defining one or more variables
101 ;; whose values specify the fontification. Font Lock mode knows of these
102 ;; variable names from (a) the buffer local variable `font-lock-defaults', if
103 ;; non-nil, or (b) the global variable `font-lock-defaults-alist', if the major
104 ;; mode has an entry. (Font Lock mode is set up via (a) where a mode's
105 ;; patterns are distributed with the mode's package library, and (b) where a
106 ;; mode's patterns are distributed with font-lock.el itself. An example of (a)
107 ;; is Pascal mode, an example of (b) is Lisp mode. Normally, the mechanism is
108 ;; (a); (b) is used where it is not clear which package library should contain
109 ;; the pattern definitions.) Font Lock mode chooses which variable to use for
110 ;; fontification based on `font-lock-maximum-decoration'.
111 ;;
112 ;; Font Lock mode fontification behaviour can be modified in a number of ways.
113 ;; See the below comments and the comments distributed throughout this file.
115 ;;; Constructing patterns:
117 ;; See the documentation for the variable `font-lock-keywords'.
118 ;;
119 ;; Efficient regexps for use as MATCHERs for `font-lock-keywords' and
120 ;; `font-lock-syntactic-keywords' can be generated via the function
121 ;; `regexp-opt', and their depth counted via the function `regexp-opt-depth'.
123 ;;; Adding patterns for modes that already support Font Lock:
125 ;; Though Font Lock highlighting patterns already exist for many modes, it's
126 ;; likely there's something that you want fontified that currently isn't, even
127 ;; at the maximum fontification level. You can add highlighting patterns via
128 ;; `font-lock-add-keywords'. For example, say in some C
129 ;; header file you #define the token `and' to expand to `&&', etc., to make
130 ;; your C code almost readable. In your ~/.emacs there could be:
131 ;;
132 ;; (font-lock-add-keywords 'c-mode '("\\<\\(and\\|or\\|not\\)\\>"))
133 ;;
134 ;; Some modes provide specific ways to modify patterns based on the values of
135 ;; other variables. For example, additional C types can be specified via the
136 ;; variable `c-font-lock-extra-types'.
138 ;;; Adding patterns for modes that do not support Font Lock:
140 ;; Not all modes support Font Lock mode. If you (as a user of the mode) add
141 ;; patterns for a new mode, you must define in your ~/.emacs a variable or
142 ;; variables that specify regexp fontification. Then, you should indicate to
143 ;; Font Lock mode, via the mode hook setting `font-lock-defaults', exactly what
144 ;; support is required. For example, say Foo mode should have the following
145 ;; regexps fontified case-sensitively, and comments and strings should not be
146 ;; fontified automagically. In your ~/.emacs there could be:
147 ;;
148 ;; (defvar foo-font-lock-keywords
149 ;; '(("\\<\\(one\\|two\\|three\\)\\>" . font-lock-keyword-face)
150 ;; ("\\<\\(four\\|five\\|six\\)\\>" . font-lock-type-face))
151 ;; "Default expressions to highlight in Foo mode.")
152 ;;
153 ;; (add-hook 'foo-mode-hook
154 ;; (function (lambda ()
155 ;; (make-local-variable 'font-lock-defaults)
156 ;; (setq font-lock-defaults '(foo-font-lock-keywords t)))))
158 ;;; Adding Font Lock support for modes:
160 ;; Of course, it would be better that the mode already supports Font Lock mode.
161 ;; The package author would do something similar to above. The mode must
162 ;; define at the top-level a variable or variables that specify regexp
163 ;; fontification. Then, the mode command should indicate to Font Lock mode,
164 ;; via `font-lock-defaults', exactly what support is required. For example,
165 ;; say Bar mode should have the following regexps fontified case-insensitively,
166 ;; and comments and strings should be fontified automagically. In bar.el there
167 ;; could be:
168 ;;
169 ;; (defvar bar-font-lock-keywords
170 ;; '(("\\<\\(uno\\|due\\|tre\\)\\>" . font-lock-keyword-face)
171 ;; ("\\<\\(quattro\\|cinque\\|sei\\)\\>" . font-lock-type-face))
172 ;; "Default expressions to highlight in Bar mode.")
173 ;;
174 ;; and within `bar-mode' there could be:
175 ;;
176 ;; (make-local-variable 'font-lock-defaults)
177 ;; (setq font-lock-defaults '(bar-font-lock-keywords nil t))
178 \f
179 ;; What is fontification for? You might say, "It's to make my code look nice."
180 ;; I think it should be for adding information in the form of cues. These cues
181 ;; should provide you with enough information to both (a) distinguish between
182 ;; different items, and (b) identify the item meanings, without having to read
183 ;; the items and think about it. Therefore, fontification allows you to think
184 ;; less about, say, the structure of code, and more about, say, why the code
185 ;; doesn't work. Or maybe it allows you to think less and drift off to sleep.
186 ;;
187 ;; So, here are my opinions/advice/guidelines:
188 ;;
189 ;; - Highlight conceptual objects, such as function and variable names, and
190 ;; different objects types differently, i.e., (a) and (b) above, highlight
191 ;; function names differently to variable names.
192 ;; - Keep the faces distinct from each other as far as possible.
193 ;; i.e., (a) above.
194 ;; - Use the same face for the same conceptual object, across all modes.
195 ;; i.e., (b) above, all modes that have items that can be thought of as, say,
196 ;; keywords, should be highlighted with the same face, etc.
197 ;; - Make the face attributes fit the concept as far as possible.
198 ;; i.e., function names might be a bold colour such as blue, comments might
199 ;; be a bright colour such as red, character strings might be brown, because,
200 ;; err, strings are brown (that was not the reason, please believe me).
201 ;; - Don't use a non-nil OVERRIDE unless you have a good reason.
202 ;; Only use OVERRIDE for special things that are easy to define, such as the
203 ;; way `...' quotes are treated in strings and comments in Emacs Lisp mode.
204 ;; Don't use it to, say, highlight keywords in commented out code or strings.
205 ;; - Err, that's it.
206 \f
207 ;;; Code:
209 ;; Define core `font-lock' group.
211 "Font Lock mode text highlighting package."
217 "Faces for highlighting text."
222 "Extra mode-specific type names for highlighting declarations."
225 ;; Define support mode groups here to impose `font-lock' group order.
227 "Font Lock support mode to cache fontification."
233 "Font Lock support mode to fontify lazily."
239 "Font Lock support mode to fontify just-in-time."
244 \f
245 ;; User variables.
248 "*Maximum size of a buffer for buffer fontification.
249 Only buffers less than this can be fontified when Font Lock mode is turned on.
250 If nil, means size is irrelevant.
251 If a list, each element should be a cons pair of the form (MAJOR-MODE . SIZE),
252 where MAJOR-MODE is a symbol or t (meaning the default). For example:
253 ((c-mode . 256000) (c++-mode . 256000) (rmail-mode . 1048576))
254 means that the maximum size is 250K for buffers in C or C++ modes, one megabyte
255 for buffers in Rmail mode, and size is irrelevant otherwise."
270 "*Maximum decoration level for fontification.
271 If nil, use the default decoration (typically the minimum available).
272 If t, use the maximum decoration available.
273 If a number, use that level of decoration (or if not available the maximum).
274 If a list, each element should be a cons pair of the form (MAJOR-MODE . LEVEL),
275 where MAJOR-MODE is a symbol or t (meaning the default). For example:
276 ((c-mode . t) (c++-mode . 2) (t . 1))
277 means use the maximum decoration available for buffers in C mode, level 2
278 decoration for buffers in C++ mode, and level 1 decoration otherwise."
295 "*If non-nil, means show status messages for buffer fontification.
296 If a number, only buffers greater than this size have fontification messages."
301 \f
302 ;; Fontification variables:
305 "A list of the keywords to highlight.
306 Each element should have one of these forms:
308 MATCHER
309 (MATCHER . MATCH)
310 (MATCHER . FACENAME)
311 (MATCHER . HIGHLIGHT)
312 (MATCHER HIGHLIGHT ...)
313 (eval . FORM)
315 where HIGHLIGHT should be either MATCH-HIGHLIGHT or MATCH-ANCHORED.
317 FORM is an expression, whose value should be a keyword element, evaluated when
318 the keyword is (first) used in a buffer. This feature can be used to provide a
319 keyword that can only be generated when Font Lock mode is actually turned on.
322 typically only MATCH-HIGHLIGHT is required.
323 However, if an item or (typically) items are to be highlighted following the
324 instance of another item (the anchor), for example each instance of the
327 MATCH-HIGHLIGHT should be of the form:
329 (MATCH FACENAME OVERRIDE LAXMATCH)
331 where MATCHER can be either the regexp to search for, or the function name to
332 call to make the search (called with one argument, the limit of the search) and
333 return non-nil if it succeeds (and set `match-data' appropriately).
334 MATCHER regexps can be generated via the function `regexp-opt'. MATCH is the
335 subexpression of MATCHER to be highlighted. MATCH can be calculated via the
336 function `regexp-opt-depth'. FACENAME is an expression whose value is the face
339 OVERRIDE and LAXMATCH are flags. If OVERRIDE is t, existing fontification can
340 be overwritten. If `keep', only parts not already fontified are highlighted.
341 If `prepend' or `append', existing fontification is merged with the new, in
342 which the new or existing fontification, respectively, takes precedence.
343 If LAXMATCH is non-nil, no error is signaled if there is no MATCH in MATCHER.
345 For example, an element of the form highlights (if not already highlighted):
348 variable `font-lock-keyword-face'.
350 the value of `font-lock-keyword-face'.
354 of `foo-bar-face', even if already highlighted.
355 (fubar-match 1 fubar-face)
356 the first subexpression within all occurrences of
357 whatever the function `fubar-match' finds and matches
358 in the value of `fubar-face'.
360 MATCH-ANCHORED should be of the form:
362 (MATCHER PRE-MATCH-FORM POST-MATCH-FORM MATCH-HIGHLIGHT ...)
364 where MATCHER is a regexp to search for or the function name to call to make
365 the search, as for MATCH-HIGHLIGHT above, but with one exception; see below.
366 PRE-MATCH-FORM and POST-MATCH-FORM are evaluated before the first, and after
367 the last, instance MATCH-ANCHORED's MATCHER is used. Therefore they can be
368 used to initialise before, and cleanup after, MATCHER is used. Typically,
369 PRE-MATCH-FORM is used to move to some position relative to the original
370 MATCHER, before starting with MATCH-ANCHORED's MATCHER. POST-MATCH-FORM might
371 be used to move, before resuming with MATCH-ANCHORED's parent's MATCHER.
373 For example, an element of the form highlights (if not already highlighted):
384 The above-mentioned exception is as follows. The limit of the MATCHER search
385 defaults to the end of the line after PRE-MATCH-FORM is evaluated.
386 However, if PRE-MATCH-FORM returns a position greater than the position after
387 PRE-MATCH-FORM is evaluated, that position is used as the limit of the search.
388 It is generally a bad idea to return a position greater than the end of the
389 line, i.e., cause the MATCHER search to span lines.
391 These regular expressions should not match text which spans lines. While
393 when you edit the buffer does not, since it considers text one line at a time.
395 This variable is set by major modes via the variable `font-lock-defaults'.
396 Be careful when composing regexps for this list; a poorly written pattern can
399 ;; This variable is used by mode packages that support Font Lock mode by
400 ;; defining their own keywords to use for `font-lock-keywords'. (The mode
401 ;; command should make it buffer-local and set it to provide the set up.)
403 "Defaults for Font Lock mode specified by the major mode.
404 Defaults should be of the form:
406 (KEYWORDS KEYWORDS-ONLY CASE-FOLD SYNTAX-ALIST SYNTAX-BEGIN ...)
408 KEYWORDS may be a symbol (a variable or function whose value is the keywords to
409 use for fontification) or a list of symbols. If KEYWORDS-ONLY is non-nil,
410 syntactic fontification (strings and comments) is not performed.
411 If CASE-FOLD is non-nil, the case of the keywords is ignored when fontifying.
412 If SYNTAX-ALIST is non-nil, it should be a list of cons pairs of the form
413 \(CHAR-OR-STRING . STRING) used to set the local Font Lock syntax table, for
414 keyword and syntactic fontification (see `modify-syntax-entry').
416 If SYNTAX-BEGIN is non-nil, it should be a function with no args used to move
417 backwards outside any enclosing syntactic block, for syntactic fontification.
418 Typical values are `beginning-of-line' (i.e., the start of the line is known to
419 be outside a syntactic block), or `beginning-of-defun' for programming modes or
420 `backward-paragraph' for textual modes (i.e., the mode-dependent function is
421 known to move outside a syntactic block). If nil, the beginning of the buffer
422 is used as a position outside of a syntactic block, in the worst case.
424 These item elements are used by Font Lock mode to set the variables
425 `font-lock-keywords', `font-lock-keywords-only',
426 `font-lock-keywords-case-fold-search', `font-lock-syntax-table' and
427 `font-lock-beginning-of-syntax-function', respectively.
429 Further item elements are alists of the form (VARIABLE . VALUE) and are in no
430 particular order. Each VARIABLE is made buffer-local before set to VALUE.
432 Currently, appropriate variables include `font-lock-mark-block-function'.
433 If this is non-nil, it should be a function with no args used to mark any
435 Typical values are `mark-defun' for programming modes or `mark-paragraph' for
436 textual modes (i.e., the mode-dependent function is known to put point and mark
437 around a text block relevant to that mode).
439 Other variables include that for syntactic keyword fontification,
440 `font-lock-syntactic-keywords'
441 and those for buffer-specialised fontification functions,
442 `font-lock-fontify-buffer-function', `font-lock-unfontify-buffer-function',
443 `font-lock-fontify-region-function', `font-lock-unfontify-region-function',
446 ;; This variable is used where font-lock.el itself supplies the keywords.
449 ;; Thus the calculation of the cache is usually faster but not
450 ;; infallible, so we risk mis-fontification. sm.
453 c-font-lock-keywords-2 c-font-lock-keywords-3)
463 objc-font-lock-keywords-2 objc-font-lock-keywords-3)
468 java-font-lock-keywords-2 java-font-lock-keywords-3)
473 lisp-font-lock-keywords-1 lisp-font-lock-keywords-2)
476 ;; For TeX modes we could use `backward-paragraph' for the same reason.
477 ;; But we don't, because paragraph breaks are arguably likely enough to
478 ;; occur within a genuine syntactic block to make it too risky.
479 ;; However, we do specify a MARK-BLOCK function as that cannot result
480 ;; in a mis-fontification even if it might not fontify enough. sm.
483 tex-font-lock-keywords-1 tex-font-lock-keywords-2)
486 )
499 "Alist of fall-back Font Lock defaults for major modes.
500 Each item should be a list of the form:
502 (MAJOR-MODE . FONT-LOCK-DEFAULTS)
504 where MAJOR-MODE is a symbol and FONT-LOCK-DEFAULTS is a list of default
508 "*Alist of `font-lock-keywords' local to a `major-mode'.
512 "*Non-nil means Font Lock should not fontify comments or strings.
516 "*Non-nil means the patterns in `font-lock-keywords' are case-insensitive.
520 "A list of the syntactic keywords to highlight.
521 Can be the list or the name of a function or variable whose value is the list.
522 See `font-lock-keywords' for a description of the form of this list;
523 the differences are listed below. MATCH-HIGHLIGHT should be of the form:
525 (MATCH SYNTAX OVERRIDE LAXMATCH)
527 where SYNTAX can be of the form (SYNTAX-CODE . MATCHING-CHAR), the name of a
528 syntax table, or an expression whose value is such a form or a syntax table.
529 OVERRIDE cannot be `prepend' or `append'.
531 For example, an element of the form highlights syntactically:
535 a hash character when following a dollar character, with a SYNTAX-CODE of
536 1 (meaning punctuation syntax). Assuming that the buffer syntax table does
537 specify hash characters to have comment start syntax, the element will only
538 highlight hash characters that do not follow dollar characters as comments
539 syntactically.
542 (1 (7 . ?'))
543 (2 (7 . ?')))
545 both single quotes which surround a single character, with a SYNTAX-CODE of
546 7 (meaning string quote syntax) and a MATCHING-CHAR of a single quote (meaning
547 a single quote matches a single quote). Assuming that the buffer syntax table
548 does not specify single quotes to have quote syntax, the element will only
549 highlight single quotes of the form 'c' as strings syntactically.
550 Other forms, such as foo'bar or 'fubar', will not be highlighted as strings.
555 "Non-nil means use this syntax table for fontifying.
556 If this is nil, the major mode's syntax table is used.
559 ;; If this is nil, we only use the beginning of the buffer if we can't use
560 ;; `font-lock-cache-position' and `font-lock-cache-state'.
562 "*Non-nil means use this function to move back outside of a syntactic block.
563 When called with no args it should leave point at the beginning of any
564 enclosing syntactic block.
565 If this is nil, the beginning of the buffer is used (in the worst case).
569 "*Non-nil means use this function to mark a block of text.
570 When called with no args it should leave point at the beginning of any
571 enclosing textual block and mark at the end.
575 "Function to use for fontifying the buffer.
579 "Function to use for unfontifying the buffer.
580 This is used when turning off Font Lock mode.
584 "Function to use for fontifying a region.
585 It should take two args, the beginning and end of the region, and an optional
586 third arg VERBOSE. If non-nil, the function should print status messages.
590 "Function to use for unfontifying a region.
591 It should take two args, the beginning and end of the region.
595 "List of Font Lock mode related modes that should not be turned on.
596 Currently, valid mode names are `fast-lock-mode', `jit-lock-mode' and
600 "Whether font-lock should cater to multiline keywords.
601 If nil, don't try to handle multiline patterns.
602 If t, always handle multiline patterns.
603 If `undecided', don't try to handle multiline patterns until you see one.
609 ;;;###autoload
612 \f
613 ;; Font Lock mode.
616 ;;
617 ;; We don't do this at the top-level as we only use non-autoloaded macros.
619 ;;
620 ;; Borrowed from lazy-lock.el.
621 ;; We use this to preserve or protect things when modifying text properties.
623 "Bind variables according to VARLIST and eval BODY restoring buffer state."
627 before-change-functions after-change-functions
628 deactivate-mark buffer-file-name buffer-file-truename))))
633 ;;
634 ;; Shut up the byte compiler.
640 ;;;###autoload
642 "Toggle Font Lock mode.
643 With arg, turn Font Lock mode on if and only if arg is positive.
645 When Font Lock mode is enabled, text is fontified as you type it:
647 - Comments are displayed in `font-lock-comment-face';
648 - Strings are displayed in `font-lock-string-face';
649 - Certain other expressions are displayed in other faces according to the
650 value of the variable `font-lock-keywords'.
652 You can enable Font Lock mode in any major mode automatically by turning on in
653 the major mode's hook. For example, put in your ~/.emacs:
655 (add-hook 'c-mode-hook 'turn-on-font-lock)
657 Alternatively, you can use Global Font Lock mode to automagically turn on Font
658 Lock mode in buffers whose major mode supports it and whose major mode is one
659 of `font-lock-global-modes'. For example, put in your ~/.emacs:
661 (global-font-lock-mode t)
663 There are a number of support modes that may be used to speed up Font Lock mode
664 in various ways, specified via the variable `font-lock-support-mode'. Where
665 major modes support different levels of fontification, you can use the variable
666 `font-lock-maximum-decoration' to specify which level you generally prefer.
667 When you turn Font Lock mode on/off the buffer is fontified/defontified, though
668 fontification occurs only if the buffer is less than `font-lock-maximum-size'.
670 For example, to specify that Font Lock mode use use Lazy Lock mode as a support
671 mode and use maximum levels of fontification, put in your ~/.emacs:
673 (setq font-lock-support-mode 'lazy-lock-mode)
674 (setq font-lock-maximum-decoration t)
676 To add your own highlighting for some major mode, and modify the highlighting
677 selected automatically via the variable `font-lock-maximum-decoration', you can
678 use `font-lock-add-keywords'.
680 To fontify a buffer, without turning on Font Lock mode and regardless of buffer
683 To fontify a block (the function or paragraph containing point, or a number of
684 lines around point), perhaps because modification on the current line caused
687 See the variable `font-lock-defaults-alist' for the Font Lock mode default
688 settings. You can set your own default settings for some mode, by setting a
689 buffer local value for `font-lock-defaults', via its mode hook."
691 ;; Don't turn on Font Lock mode if we don't have a display (we're running a
692 ;; batch job) or if the buffer is invisible (the name starts with a space).
699 ;; Turn on Font Lock mode.
706 ;; Fontify the buffer if we have to.
709 nil)
714 ;; Turn off Font Lock mode.
722 ;;;###autoload
724 "Turn on Font Lock mode conditionally.
725 Turn on only if the terminal can display it."
729 ;;;###autoload
731 "Add highlighting KEYWORDS for MODE.
732 MODE should be a symbol, the major mode command name, such as `c-mode'
733 or nil. If nil, highlighting keywords are added for the current buffer.
734 KEYWORDS should be a list; see the variable `font-lock-keywords'.
735 By default they are added at the beginning of the current highlighting list.
736 If optional argument APPEND is `set', they are used to replace the current
737 highlighting list. If APPEND is any other non-nil value, they are added at the
738 end of the current highlighting list.
740 For example:
742 (font-lock-add-keywords 'c-mode
746 adds two fontification patterns for C mode, to fontify `FIXME:' words, even in
747 comments, and to fontify `and', `or' and `not' words as keywords.
749 Note that some modes have specialised support for additional patterns, e.g.,
750 see the variables `c-font-lock-extra-types', `c++-font-lock-extra-types',
751 `objc-font-lock-extra-types' and `java-font-lock-extra-types'."
753 ;; If MODE is non-nil, add the KEYWORDS and APPEND spec to
754 ;; `font-lock-keywords-alist' so `font-lock-set-defaults' uses them.
760 ;; Otherwise if Font Lock mode is on, set or add the keywords now.
766 font-lock-keywords)))
771 ;;;###autoload
773 "Remove highlighting KEYWORDS from the current buffer.
774 A non-nil MODE is currently unsupported."
780 font-lock-keywords)))))
782 \f
783 ;;; Global Font Lock mode.
785 ;; A few people have hassled in the past for a way to make it easier to turn on
786 ;; Font Lock mode, without the user needing to know for which modes s/he has to
787 ;; turn it on, perhaps the same way hilit19.el/hl319.el does. I've always
788 ;; balked at that way, as I see it as just re-moulding the same problem in
789 ;; another form. That is; some person would still have to keep track of which
790 ;; modes (which may not even be distributed with Emacs) support Font Lock mode.
791 ;; The list would always be out of date. And that person might have to be me.
793 ;; Implementation.
794 ;;
795 ;; In a previous discussion the following hack came to mind. It is a gross
796 ;; hack, but it generally works. We use the convention that major modes start
797 ;; by calling the function `kill-all-local-variables', which in turn runs
798 ;; functions on the hook variable `change-major-mode-hook'. We attach our
799 ;; function `font-lock-change-major-mode' to that hook. Of course, when this
800 ;; hook is run, the major mode is in the process of being changed and we do not
801 ;; know what the final major mode will be. So, `font-lock-change-major-mode'
802 ;; only (a) notes the name of the current buffer, and (b) adds our function
803 ;; `turn-on-font-lock-if-enabled' to the hook variables `find-file-hooks' and
804 ;; `post-command-hook' (for buffers that are not visiting files). By the time
805 ;; the functions on the first of these hooks to be run are run, the new major
806 ;; mode is assumed to be in place. This way we get a Font Lock function run
807 ;; when a major mode is turned on, without knowing major modes or their hooks.
808 ;;
809 ;; Naturally this requires that (a) major modes run `kill-all-local-variables',
810 ;; as they are supposed to do, and (b) the major mode is in place after the
811 ;; file is visited or the command that ran `kill-all-local-variables' has
812 ;; finished, whichever the sooner. Arguably, any major mode that does not
813 ;; follow the convension (a) is broken, and I can't think of any reason why (b)
814 ;; would not be met (except `gnudoit' on non-files). However, it is not clean.
815 ;;
816 ;; Probably the cleanest solution is to have each major mode function run some
817 ;; hook, e.g., `major-mode-hook', but maybe implementing that change is
818 ;; impractical. I am personally against making `setq' a macro or be advised,
819 ;; or have a special function such as `set-major-mode', but maybe someone can
820 ;; come up with another solution?
822 ;; User interface.
823 ;;
824 ;; Although Global Font Lock mode is a pseudo-mode, I think that the user
825 ;; interface should conform to the usual Emacs convention for modes, i.e., a
826 ;; command to toggle the feature (`global-font-lock-mode') with a variable for
827 ;; finer control of the mode's behaviour (`font-lock-global-modes').
828 ;;
829 ;; The feature should not be enabled by loading font-lock.el, since other
830 ;; mechanisms for turning on Font Lock mode, such as M-x font-lock-mode RET or
831 ;; (add-hook 'c-mode-hook 'turn-on-font-lock), would cause Font Lock mode to be
832 ;; turned on everywhere. That would not be intuitive or informative because
833 ;; loading a file tells you nothing about the feature or how to control it. It
834 ;; would also be contrary to the Principle of Least Surprise. sm.
838 ;;;###autoload
840 "Toggle Global Font Lock mode.
841 With prefix ARG, turn Global Font Lock mode on if and only if ARG is positive.
842 Displays a message saying whether the mode is on or off if MESSAGE is non-nil.
843 Returns the new status of Global Font Lock mode (non-nil means on).
845 When Global Font Lock mode is enabled, Font Lock mode is automagically
846 turned on in a buffer if its major mode is one of `font-lock-global-modes'."
866 ;; This variable was originally a `defvar' to keep track of
867 ;; whether Global Font Lock mode was turned on or not. As a `defcustom' with
868 ;; special `:set' and `:require' forms, we can provide custom mode control.
869 ;;;###autoload
871 "Toggle Global Font Lock mode.
872 When Global Font Lock mode is enabled, Font Lock mode is automagically
873 turned on in a buffer if its major mode is one of `font-lock-global-modes'.
874 Setting this variable directly does not take effect;
884 "*Modes for which Font Lock mode is automagically turned on.
885 Global Font Lock mode is controlled by the command `global-font-lock-mode'.
886 If nil, means no modes have Font Lock mode automatically turned on.
887 If t, all modes that support Font Lock mode have it automatically turned on.
888 If a list, it should be a list of `major-mode' symbol names for which Font Lock
889 mode should be automatically turned on. The sense of the list is negated if it
890 begins with `not'. For example:
891 (c-mode c++-mode)
892 means that Font Lock mode is turned on for buffers in C and C++ modes only."
902 ;; Turn off Font Lock mode if it's on.
905 ;; Gross hack warning: Delicate readers should avert eyes now.
906 ;; Something is running `kill-all-local-variables', which generally means the
907 ;; major mode is being changed. Run `turn-on-font-lock-if-enabled' after the
908 ;; file is visited or the current command has finished.
914 ;; Gross hack warning: Delicate readers should avert eyes now.
915 ;; Turn on Font Lock mode if it's supported by the major mode and enabled by
916 ;; the user.
934 ;;; End of Global Font Lock mode.
935 \f
936 ;;; Font Lock Support mode.
938 ;; This is the code used to interface font-lock.el with any of its add-on
939 ;; packages, and provide the user interface. Packages that have their own
940 ;; local buffer fontification functions (see below) may have to call
941 ;; `font-lock-after-fontify-buffer' and/or `font-lock-after-unfontify-buffer'
942 ;; themselves.
945 "*Support mode for Font Lock mode.
946 Support modes speed up Font Lock mode by being choosy about when fontification
947 occurs. Known support modes are Fast Lock mode (symbol `fast-lock-mode'),
948 Lazy Lock mode (symbol `lazy-lock-mode'), and Just-in-time Lock mode (symbol
949 `jit-lock-mode'. See those modes for more info.
950 If nil, means support for Font Lock mode is never performed.
951 If a symbol, use that support mode.
952 If a list, each element should be of the form (MAJOR-MODE . SUPPORT-MODE),
953 where MAJOR-MODE is a symbol or t (meaning the default). For example:
954 ((c-mode . fast-lock-mode) (c++-mode . fast-lock-mode) (t . lazy-lock-mode))
955 means that Fast Lock mode is used to support Font Lock mode for buffers in C or
956 C++ modes, and Lazy Lock mode is used to support Font Lock mode otherwise.
958 The value of this variable is used when Font Lock mode is turned on."
974 ))
1014 ;;; End of Font Lock Support mode.
1015 \f
1016 ;;; Fontification functions.
1018 ;; Rather than the function, e.g., `font-lock-fontify-region' containing the
1019 ;; code to fontify a region, the function runs the function whose name is the
1020 ;; value of the variable, e.g., `font-lock-fontify-region-function'. Normally,
1021 ;; the value of this variable is, e.g., `font-lock-default-fontify-region'
1022 ;; which does contain the code to fontify a region. However, the value of the
1023 ;; variable could be anything and thus, e.g., `font-lock-fontify-region' could
1024 ;; do anything. The indirection of the fontification functions gives major
1025 ;; modes the capability of modifying the way font-lock.el fontifies. Major
1026 ;; modes can modify the values of, e.g., `font-lock-fontify-region-function',
1027 ;; via the variable `font-lock-defaults'.
1028 ;;
1029 ;; For example, Rmail mode sets the variable `font-lock-defaults' so that
1030 ;; font-lock.el uses its own function for buffer fontification. This function
1031 ;; makes fontification be on a message-by-message basis and so visiting an
1032 ;; RMAIL file is much faster. A clever implementation of the function might
1033 ;; fontify the headers differently than the message body. (It should, and
1034 ;; correspondingly for Mail mode, but I can't be bothered to do the work. Can
1035 ;; you?) This hints at a more interesting use...
1036 ;;
1037 ;; Languages that contain text normally contained in different major modes
1038 ;; could define their own fontification functions that treat text differently
1039 ;; depending on its context. For example, Perl mode could arrange that here
1040 ;; docs are fontified differently than Perl code. Or Yacc mode could fontify
1041 ;; rules one way and C code another. Neat!
1042 ;;
1043 ;; A further reason to use the fontification indirection feature is when the
1044 ;; default syntactual fontification, or the default fontification in general,
1045 ;; is not flexible enough for a particular major mode. For example, perhaps
1046 ;; comments are just too hairy for `font-lock-fontify-syntactically-region' to
1047 ;; cope with. You need to write your own version of that function, e.g.,
1048 ;; `hairy-fontify-syntactically-region', and make your own version of
1049 ;; `hairy-fontify-region' call that function before calling
1050 ;; `font-lock-fontify-keywords-region' for the normal regexp fontification
1051 ;; pass. And Hairy mode would set `font-lock-defaults' so that font-lock.el
1052 ;; would call your region fontification function instead of its own. For
1053 ;; example, TeX modes could fontify {\foo ...} and \bar{...} etc. multi-line
1054 ;; directives correctly and cleanly. (It is the same problem as fontifying
1055 ;; multi-line strings and comments; regexps are not appropriate for the job.)
1057 ;;;###autoload
1059 "Fontify the current buffer the way the function `font-lock-mode' would."
1076 font-lock-verbose)))
1080 ;; Make sure we have the right `font-lock-keywords' etc.
1083 ;; Make sure we fontify etc. in the whole buffer.
1092 ;; We don't restore the old fontification, so it's best to unfontify.
1094 ;; Make sure we undo `font-lock-keywords' etc.
1099 ;; Make sure we unfontify etc. in the whole buffer.
1113 ;; Use the fontification syntax table, if any.
1116 ;; check to see if we should expand the beg/end area for
1117 ;; proper multiline matches
1119 ;; if the text-property is non-nil, (1+ beg)
1120 ;; is valid. We need to use (1+ beg) for the
1121 ;; case where (get-text-property (1- beg)) is nil
1122 ;; in which case we want to keep BEG but
1123 ;; previous-single-property-change will return
1124 ;; the previous change (if any) rather than
1125 ;; the one at BEG.
1129 beg))
1133 ;; Now do the fontification.
1140 ;; Clean up.
1143 ;; The following must be rethought, since keywords can override fontification.
1144 ; ;; Now scan for keywords, but not if we are inside a comment now.
1145 ; (or (and (not font-lock-keywords-only)
1146 ; (let ((state (parse-partial-sexp beg end nil nil
1147 ; font-lock-cache-state)))
1148 ; (or (nth 4 state) (nth 7 state))))
1149 ; (font-lock-fontify-keywords-region beg end))
1158 ;; Called when any modification is made to buffer text.
1163 ;; Rescan between start of lines enclosing the region.
1169 "Fontify some lines the way `font-lock-fontify-buffer' would.
1170 The lines could be a function or paragraph, or a specified number of lines.
1171 If ARG is given, fontify that many lines before and after point, or 16 lines if
1172 no ARG is given and `font-lock-mark-block-function' is nil.
1173 If `font-lock-mark-block-function' non-nil and no ARG is given, it is used to
1174 delimit the region to fontify."
1177 deactivate-mark)
1178 ;; Make sure we have the right `font-lock-keywords' etc.
1194 ;;; End of Fontification functions.
1195 \f
1196 ;;; Additional text property functions.
1198 ;; The following text property functions should be builtins. This means they
1199 ;; should be written in C and put with all the other text property functions.
1200 ;; In the meantime, those that are used by font-lock.el are defined in Lisp
1201 ;; below and given a `font-lock-' prefix. Those that are not used are defined
1202 ;; in Lisp below and commented out. sm.
1205 "Prepend to one property of the text from START to END.
1206 Arguments PROP and VALUE specify the property and value to prepend to the value
1207 already in place. The resulting property values are always lists.
1208 Optional argument OBJECT is the string or buffer containing the text."
1215 object)
1219 "Append to one property of the text from START to END.
1220 Arguments PROP and VALUE specify the property and value to append to the value
1221 already in place. The resulting property values are always lists.
1222 Optional argument OBJECT is the string or buffer containing the text."
1229 object)
1233 "Fill in one property of the text from START to END.
1234 Arguments PROP and VALUE specify the property and value to put where none are
1235 already in place. Therefore existing property values are not overwritten.
1236 Optional argument OBJECT is the string or buffer containing the text."
1243 ;; For completeness: this is to `remove-text-properties' as `put-text-property'
1244 ;; is to `add-text-properties', etc.
1245 ;(defun remove-text-property (start end property &optional object)
1246 ; "Remove a property from text from START to END.
1247 ;Argument PROPERTY is the property to remove.
1248 ;Optional argument OBJECT is the string or buffer containing the text.
1249 ;Return t if the property was actually removed, nil otherwise."
1250 ; (remove-text-properties start end (list property) object))
1252 ;; For consistency: maybe this should be called `remove-single-property' like
1253 ;; `next-single-property-change' (not `next-single-text-property-change'), etc.
1254 ;(defun remove-single-text-property (start end prop value &optional object)
1255 ; "Remove a specific property value from text from START to END.
1256 ;Arguments PROP and VALUE specify the property and value to remove. The
1257 ;resulting property values are not equal to VALUE nor lists containing VALUE.
1258 ;Optional argument OBJECT is the string or buffer containing the text."
1259 ; (let ((start (text-property-not-all start end prop nil object)) next prev)
1260 ; (while start
1261 ; (setq next (next-single-property-change start prop object end)
1262 ; prev (get-text-property start prop object))
1263 ; (cond ((and (symbolp prev) (eq value prev))
1264 ; (remove-text-property start next prop object))
1265 ; ((and (listp prev) (memq value prev))
1266 ; (let ((new (delq value prev)))
1267 ; (cond ((null new)
1268 ; (remove-text-property start next prop object))
1269 ; ((= (length new) 1)
1270 ; (put-text-property start next prop (car new) object))
1271 ; (t
1272 ; (put-text-property start next prop new object))))))
1273 ; (setq start (text-property-not-all next end prop nil object)))))
1275 ;;; End of Additional text property functions.
1276 \f
1277 ;;; Syntactic regexp fontification functions.
1279 ;; These syntactic keyword pass functions are identical to those keyword pass
1280 ;; functions below, with the following exceptions; (a) they operate on
1281 ;; `font-lock-syntactic-keywords' of course, (b) they are all `defun' as speed
1282 ;; is less of an issue, (c) eval of property value does not occur JIT as speed
1283 ;; is less of an issue, (d) OVERRIDE cannot be `prepend' or `append' as it
1284 ;; makes no sense for `syntax-table' property values, (e) they do not do it
1285 ;; LOUDLY as it is not likely to be intensive.
1288 "Apply HIGHLIGHT following a match.
1289 HIGHLIGHT should be of the form MATCH-HIGHLIGHT,
1290 see `font-lock-syntactic-keywords'."
1298 ;; No match but we might not signal an error.
1302 ;; Cannot override existing fontification.
1306 ;; Override existing fontification.
1309 ;; Keep existing fontification.
1313 "Fontify according to KEYWORDS until LIMIT.
1314 KEYWORDS should be of the form MATCH-ANCHORED, see `font-lock-keywords',
1315 LIMIT can be modified by the value of its PRE-MATCH-FORM."
1317 ;; Evaluate PRE-MATCH-FORM.
1319 ;; Set LIMIT to value of PRE-MATCH-FORM or the end of line.
1324 ;; Find an occurrence of `matcher' before `limit'.
1328 ;; Apply each highlight to this instance of `matcher'.
1333 ;; Evaluate POST-MATCH-FORM.
1337 "Fontify according to `font-lock-syntactic-keywords' between START and END.
1338 START should be at the beginning of a line."
1339 ;; If `font-lock-syntactic-keywords' is a symbol, get the real keywords.
1342 font-lock-syntactic-keywords)))
1343 ;; If `font-lock-syntactic-keywords' is not compiled, compile it.
1346 font-lock-syntactic-keywords)))
1347 ;; Get down to business.
1350 keyword matcher highlights)
1352 ;; Find an occurrence of `matcher' from `start' to `end'.
1358 ;; Apply each highlight to this instance of `matcher', which may be
1359 ;; specific highlights or more keywords anchored to `matcher'.
1365 end))
1369 ;;; End of Syntactic regexp fontification functions.
1370 \f
1371 ;;; Syntactic fontification functions.
1373 ;; These record the parse state at a particular position, always the start of a
1374 ;; line. Used to make `font-lock-fontify-syntactically-region' faster.
1375 ;; Previously, `font-lock-cache-position' was just a buffer position. However,
1376 ;; under certain situations, this occasionally resulted in mis-fontification.
1377 ;; I think the "situations" were deletion with Lazy Lock mode's deferral. sm.
1382 "Put proper face on each string and comment between START and END.
1383 START should be at the beginning of a line."
1385 state string beg)
1388 ;;
1389 ;; Find the state at the `beginning-of-line' before `start'.
1391 ;; Use the cache for the state of `start'.
1393 ;; Find the state of `start'.
1395 ;; Use the state at the previous cache position, if any, or
1396 ;; otherwise calculate from `point-min'.
1400 font-lock-cache-state)))
1401 ;; Call the function to move outside any syntactic block.
1404 ;; Cache the state and position of `start'.
1407 ;;
1408 ;; If the region starts inside a string or comment, show the extent of it.
1414 font-lock-string-face
1415 font-lock-comment-face)))
1416 ;;
1417 ;; Find each interesting place between here and `end'.
1427 font-lock-string-face
1428 font-lock-comment-face)))))
1430 ;;; End of Syntactic fontification functions.
1431 \f
1432 ;;; Keyword regexp fontification functions.
1435 "Apply HIGHLIGHT following a match.
1436 HIGHLIGHT should be of the form MATCH-HIGHLIGHT, see `font-lock-keywords'."
1441 ;; No match but we might not signal an error.
1445 ;; Cannot override existing fontification.
1449 ;; Override existing fontification.
1452 ;; Prepend to existing fontification.
1455 ;; Append to existing fontification.
1458 ;; Keep existing fontification.
1462 "Fontify according to KEYWORDS until LIMIT.
1463 KEYWORDS should be of the form MATCH-ANCHORED, see `font-lock-keywords',
1464 LIMIT can be modified by the value of its PRE-MATCH-FORM."
1467 ;; Evaluate PRE-MATCH-FORM.
1469 ;; Set LIMIT to value of PRE-MATCH-FORM or the end of line.
1475 pre-match-value
1477 ;; this is a multiline anchored match
1481 ;; Find an occurrence of `matcher' before `limit'.
1485 ;; Apply each highlight to this instance of `matcher'.
1490 ;; Evaluate POST-MATCH-FORM.
1494 "Fontify according to `font-lock-keywords' between START and END.
1495 START should be at the beginning of a line."
1501 keyword matcher highlights)
1502 ;;
1503 ;; Fontify each item in `font-lock-keywords' from `start' to `end'.
1507 ;;
1508 ;; Find an occurrence of `matcher' from `start' to `end'.
1521 ;; this is a multiline regexp match
1525 ;; Apply each highlight to this instance of `matcher', which may be
1526 ;; specific highlights or more keywords anchored to `matcher'.
1535 ;;; End of Keyword regexp fontification functions.
1536 \f
1537 ;; Various functions.
1540 "Compile KEYWORDS into the form (t KEYWORD ...).
1541 Here KEYWORD is of the form (MATCHER HIGHLIGHT ...) as shown in the
1542 `font-lock-keywords' doc string."
1544 keywords
1553 ;; If FORM is a FACENAME then quote it. Otherwise ignore the quote.
1564 keyword)))
1567 "Evalulate KEYWORDS if a function (funcall) or variable (eval) name."
1569 keywords
1575 "Return value in ALIST for `major-mode', or ALIST if it is not an alist.
1576 Structure is ((MAJOR-MODE . VALUE) ...) where MAJOR-MODE may be t."
1579 alist))
1582 "Return LEVELth element of KEYWORDS.
1583 A LEVEL of nil is equal to a LEVEL of 0, a LEVEL of t is equal to
1584 \(1- (length KEYWORDS))."
1586 keywords)
1597 "Set fontification defaults appropriately for this mode.
1598 Sets various variables using `font-lock-defaults' (or, if nil, using
1599 `font-lock-defaults-alist') and `font-lock-maximum-decoration'."
1600 ;; Set fontification defaults.
1602 ;; Set iff not previously set.
1613 ;; Regexp fontification?
1616 ;; Local fontification?
1620 ;; Syntactic fontification?
1623 ;; Case fold during regexp fontification?
1626 ;; Syntax table for regexp and syntactic fontification?
1632 ;; The character to modify may be a single CHAR or a STRING.
1641 ;; Syntax function for syntactic fontification?
1645 ;; Variable alist?
1655 "Unset fontification defaults. See function `font-lock-set-defaults'."
1657 font-lock-keywords nil
1658 font-lock-keywords-only nil
1659 font-lock-keywords-case-fold-search nil
1660 font-lock-syntax-table nil
1661 font-lock-beginning-of-syntax-function nil)
1668 \f
1669 ;;; Colour etc. support.
1671 ;; Originally these variable values were face names such as `bold' etc.
1672 ;; Now we create our own faces, but we keep these variables for compatibility
1673 ;; and they give users another mechanism for changing face appearance.
1674 ;; We now allow a FACENAME in `font-lock-keywords' to be any expression that
1675 ;; returns a face. So the easiest thing is to continue using these variables,
1676 ;; rather than sometimes evaling FACENAME and sometimes not. sm.
1707 ;; Originally face attributes were specified via `font-lock-face-attributes'.
1708 ;; Users then changed the default face attributes by setting that variable.
1709 ;; However, we try and be back-compatible and respect its value if set except
1710 ;; for faces where M-x customize has been used to save changes for the face.
1716 ;; Rustle up a `defface' SPEC from a `font-lock-face-attributes' entry.
1723 face-spec)
1736 ;; But now we do it the custom way. Note that `defface' will not overwrite any
1737 ;; faces declared above via `custom-declare-face'.
1747 "Font Lock mode face used to highlight comments."
1757 "Font Lock mode face used to highlight strings."
1767 "Font Lock mode face used to highlight keywords."
1777 "Font Lock mode face used to highlight builtins."
1785 "Font Lock mode face used to highlight function names."
1797 "Font Lock mode face used to highlight variable names."
1807 "Font Lock mode face used to highlight type and classes."
1819 "Font Lock mode face used to highlight constants and labels."
1827 "Font Lock mode face used to highlight warnings."
1830 ;;; End of Colour etc. support.
1831 \f
1832 ;;; Menu support.
1834 ;; This section of code is commented out because Emacs does not have real menu
1835 ;; buttons. (We can mimic them by putting "( ) " or "(X) " at the beginning of
1836 ;; the menu entry text, but with Xt it looks both ugly and embarrassingly
1837 ;; amateur.) If/When Emacs gets real menus buttons, put in menu-bar.el after
1838 ;; the entry for "Text Properties" something like:
1839 ;;
1840 ;; (define-key menu-bar-edit-menu [font-lock]
1841 ;; (cons "Syntax Highlighting" font-lock-menu))
1842 ;;
1843 ;; and remove a single ";" from the beginning of each line in the rest of this
1844 ;; section. Probably the mechanism for telling the menu code what are menu
1845 ;; buttons and when they are on or off needs tweaking. I have assumed that the
1846 ;; mechanism is via `menu-toggle' and `menu-selected' symbol properties. sm.
1848 ;;;;###autoload
1849 ;(progn
1850 ; ;; Make the Font Lock menu.
1851 ; (defvar font-lock-menu (make-sparse-keymap "Syntax Highlighting"))
1852 ; ;; Add the menu items in reverse order.
1853 ; (define-key font-lock-menu [fontify-less]
1854 ; '("Less In Current Buffer" . font-lock-fontify-less))
1855 ; (define-key font-lock-menu [fontify-more]
1856 ; '("More In Current Buffer" . font-lock-fontify-more))
1857 ; (define-key font-lock-menu [font-lock-sep]
1858 ; '("--"))
1859 ; (define-key font-lock-menu [font-lock-mode]
1860 ; '("In Current Buffer" . font-lock-mode))
1861 ; (define-key font-lock-menu [global-font-lock-mode]
1862 ; '("In All Buffers" . global-font-lock-mode)))
1863 ;
1864 ;;;;###autoload
1865 ;(progn
1866 ; ;; We put the appropriate `menu-enable' etc. symbol property values on when
1867 ; ;; font-lock.el is loaded, so we don't need to autoload the three variables.
1868 ; (put 'global-font-lock-mode 'menu-toggle t)
1869 ; (put 'font-lock-mode 'menu-toggle t)
1870 ; (put 'font-lock-fontify-more 'menu-enable '(identity))
1871 ; (put 'font-lock-fontify-less 'menu-enable '(identity)))
1872 ;
1873 ;;; Put the appropriate symbol property values on now. See above.
1874 ;(put 'global-font-lock-mode 'menu-selected 'global-font-lock-mode)
1875 ;(put 'font-lock-mode 'menu-selected 'font-lock-mode)
1876 ;(put 'font-lock-fontify-more 'menu-enable '(nth 2 font-lock-fontify-level))
1877 ;(put 'font-lock-fontify-less 'menu-enable '(nth 1 font-lock-fontify-level))
1878 ;
1879 ;(defvar font-lock-fontify-level nil) ; For less/more fontification.
1880 ;
1881 ;(defun font-lock-fontify-level (level)
1882 ; (let ((font-lock-maximum-decoration level))
1883 ; (when font-lock-mode
1884 ; (font-lock-mode))
1885 ; (font-lock-mode)
1886 ; (when font-lock-verbose
1887 ; (message "Fontifying %s... level %d" (buffer-name) level))))
1888 ;
1889 ;(defun font-lock-fontify-less ()
1890 ; "Fontify the current buffer with less decoration.
1891 ;See `font-lock-maximum-decoration'."
1892 ; (interactive)
1893 ; ;; Check in case we get called interactively.
1894 ; (if (nth 1 font-lock-fontify-level)
1895 ; (font-lock-fontify-level (1- (car font-lock-fontify-level)))
1896 ; (error "No less decoration")))
1897 ;
1898 ;(defun font-lock-fontify-more ()
1899 ; "Fontify the current buffer with more decoration.
1900 ;See `font-lock-maximum-decoration'."
1901 ; (interactive)
1902 ; ;; Check in case we get called interactively.
1903 ; (if (nth 2 font-lock-fontify-level)
1904 ; (font-lock-fontify-level (1+ (car font-lock-fontify-level)))
1905 ; (error "No more decoration")))
1906 ;
1907 ;;; This should be called by `font-lock-set-defaults'.
1908 ;(defun font-lock-set-menu ()
1909 ; ;; Activate less/more fontification entries if there are multiple levels for
1910 ; ;; the current buffer. Sets `font-lock-fontify-level' to be of the form
1911 ; ;; (CURRENT-LEVEL IS-LOWER-LEVEL-P IS-HIGHER-LEVEL-P) for menu activation.
1912 ; (let ((keywords (or (nth 0 font-lock-defaults)
1913 ; (nth 1 (assq major-mode font-lock-defaults-alist))))
1914 ; (level (font-lock-value-in-major-mode font-lock-maximum-decoration)))
1915 ; (make-local-variable 'font-lock-fontify-level)
1916 ; (if (or (symbolp keywords) (= (length keywords) 1))
1917 ; (font-lock-unset-menu)
1918 ; (cond ((eq level t)
1919 ; (setq level (1- (length keywords))))
1920 ; ((or (null level) (zerop level))
1921 ; ;; The default level is usually, but not necessarily, level 1.
1922 ; (setq level (- (length keywords)
1923 ; (length (member (eval (car keywords))
1924 ; (mapcar 'eval (cdr keywords))))))))
1925 ; (setq font-lock-fontify-level (list level (> level 1)
1926 ; (< level (1- (length keywords))))))))
1927 ;
1928 ;;; This should be called by `font-lock-unset-defaults'.
1929 ;(defun font-lock-unset-menu ()
1930 ; ;; Deactivate less/more fontification entries.
1931 ; (setq font-lock-fontify-level nil))
1933 ;;; End of Menu support.
1934 \f
1935 ;;; Various regexp information shared by several modes.
1936 ;;; Information specific to a single mode should go in its load library.
1938 ;; Font Lock support for C, C++, Objective-C and Java modes will one day be in
1939 ;; some cc-font.el (and required by cc-mode.el). However, the below function
1940 ;; should stay in font-lock.el, since it is used by other libraries. sm.
1943 "Match, and move over, any declaration/definition item after point.
1944 Matches after point, but ignores leading whitespace and `*' characters.
1945 Does not move further than LIMIT.
1947 The expected syntax of a declaration/definition item is `word' (preceded by
1948 optional whitespace and `*' characters and proceeded by optional whitespace)
1949 optionally followed by a `('. Everything following the item (but belonging to
1950 it) is expected to by skip-able by `scan-sexps', and items are expected to be
1951 separated with a `,' and to be terminated with a `;'.
1953 Thus the regexp matches after point: word (
1954 ^^^^ ^
1955 Where the match subexpressions are: 1 2
1957 The item is delimited by (match-beginning 1) and (match-end 1).
1958 If (match-beginning 2) is non-nil, the item is followed by a `('.
1960 This function could be MATCHER in a MATCH-ANCHORED `font-lock-keywords' item."
1965 ;; Restrict to the end of line, currently guaranteed to be LIMIT.
1968 ;; Move over any item value, etc., to the next item.
1973 \f
1974 ;; Lisp.
1979 ;;
1980 ;; Definitions.
1982 ;; Function declarations.
1988 ;; Variable declarations.
1990 ;; Structure declarations.
1993 ;; Any whitespace and defined object.
2000 nil t))
2001 ;;
2002 ;; Emacs Lisp autoload cookies.
2004 ))
2011 ;;
2012 ;; Control structures. Emacs Lisp forms.
2022 "eval-when"
2029 ;;
2030 ;; Control structures. Common Lisp forms.
2044 ;;
2045 ;; Exit/Feature symbols as constants.
2050 ;;
2051 ;; Erroneous structures.
2053 ;;
2054 ;; Words inside \\[] tend to be for `substitute-command-keys'.
2056 ;;
2057 ;; Words inside `' tend to be symbol names.
2059 ;;
2060 ;; Constant values.
2062 ;;
2063 ;; ELisp and CLisp `&' keywords as types.
2065 )))
2070 \f
2071 ;; TeX.
2073 ;(defvar tex-font-lock-keywords
2074 ; ;; Regexps updated with help from Ulrik Dickow <dickow@nbi.dk>.
2075 ; '(("\\\\\\(begin\\|end\\|newcommand\\){\\([a-zA-Z0-9\\*]+\\)}"
2076 ; 2 font-lock-function-name-face)
2077 ; ("\\\\\\(cite\\|label\\|pageref\\|ref\\){\\([^} \t\n]+\\)}"
2078 ; 2 font-lock-constant-face)
2079 ; ;; It seems a bit dubious to use `bold' and `italic' faces since we might
2080 ; ;; not be able to display those fonts.
2081 ; ("{\\\\bf\\([^}]+\\)}" 1 'bold keep)
2082 ; ("{\\\\\\(em\\|it\\|sl\\)\\([^}]+\\)}" 2 'italic keep)
2083 ; ("\\\\\\([a-zA-Z@]+\\|.\\)" . font-lock-keyword-face)
2084 ; ("^[ \t\n]*\\\\def[\\\\@]\\(\\w+\\)" 1 font-lock-function-name-face keep))
2085 ; ;; Rewritten and extended for LaTeX2e by Ulrik Dickow <dickow@nbi.dk>.
2086 ; '(("\\\\\\(begin\\|end\\|newcommand\\){\\([a-zA-Z0-9\\*]+\\)}"
2087 ; 2 font-lock-function-name-face)
2088 ; ("\\\\\\(cite\\|label\\|pageref\\|ref\\){\\([^} \t\n]+\\)}"
2089 ; 2 font-lock-constant-face)
2090 ; ("^[ \t]*\\\\def\\\\\\(\\(\\w\\|@\\)+\\)" 1 font-lock-function-name-face)
2091 ; "\\\\\\([a-zA-Z@]+\\|.\\)"
2092 ; ;; It seems a bit dubious to use `bold' and `italic' faces since we might
2093 ; ;; not be able to display those fonts.
2094 ; ;; LaTeX2e: \emph{This is emphasized}.
2095 ; ("\\\\emph{\\([^}]+\\)}" 1 'italic keep)
2096 ; ;; LaTeX2e: \textbf{This is bold}, \textit{...}, \textsl{...}
2097 ; ("\\\\text\\(\\(bf\\)\\|it\\|sl\\){\\([^}]+\\)}"
2098 ; 3 (if (match-beginning 2) 'bold 'italic) keep)
2099 ; ;; Old-style bf/em/it/sl. Stop at `\\' and un-escaped `&', for tables.
2100 ; ("\\\\\\(\\(bf\\)\\|em\\|it\\|sl\\)\\>\\(\\([^}&\\]\\|\\\\[^\\]\\)+\\)"
2101 ; 3 (if (match-beginning 2) 'bold 'italic) keep))
2103 ;; Rewritten with the help of Alexandra Bac <abac@welcome.disi.unige.it>.
2107 ;; Names of commands whose arg should be fontified as heading, etc.
2109 ;; These commands have optional args.
2117 "newtheorem"
2120 t))
2124 t))
2128 t))
2132 t))
2133 ;; Miscellany.
2139 )
2141 ;;
2142 ;; Heading args.
2149 ;;
2150 ;; Variable args.
2154 ;;
2155 ;; Include args.
2162 ;;
2163 ;; Definitions. I think.
2166 )))
2173 ;; Names of commands whose arg should be fontified with fonts.
2178 ;;
2179 ;; Names of commands whose arg should be fontified as a citation.
2182 t))
2186 t))
2187 ;;
2188 ;; Names of commands that should be fontified.
2194 t))
2196 ;;
2197 ;; Miscellany.
2203 )
2205 ;;
2206 ;; Citation args.
2213 ;;
2214 ;; Command names, special and general.
2217 ;;
2218 ;; Font environments. It seems a bit dubious to use `bold' etc. faces
2219 ;; since we might not be able to display those fonts.
2229 ;;
2230 ;; Old-style bf/em/it/sl. Stop at `\\' and un-escaped `&', for tables.
2234 ))))
2239 \f
2240 ;;; User choices.
2242 ;; These provide a means to fontify types not defined by the language. Those
2243 ;; types might be the user's own or they might be generally accepted and used.
2244 ;; Generally accepted types are used to provide default variable values.
2247 "Widget `:type' for members of the custom group `font-lock-extra-types'.
2248 Members should `:load' the package `font-lock' to use this widget."
2253 "*List of extra types to fontify in C mode.
2254 Each list item should be a regexp not containing word-delimiters.
2256 ending in _t are treated as type names.
2258 The value of this variable is used when Font Lock mode is turned on."
2272 "type_info"
2275 "*List of extra types to fontify in C++ mode.
2276 Each list item should be a regexp not containing word-delimiters.
2278 name.
2280 The value of this variable is used when Font Lock mode is turned on."
2285 "*List of extra types to fontify in Objective-C mode.
2286 Each list item should be a regexp not containing word-delimiters.
2288 Class, BOOL, IMP and SEL are treated as type names.
2290 The value of this variable is used when Font Lock mode is turned on."
2296 "*List of extra types to fontify in Java mode.
2297 Each list item should be a regexp not containing word-delimiters.
2299 words (and words conforming to the Java id spec) are treated as type names.
2301 The value of this variable is used when Font Lock mode is turned on."
2304 \f
2305 ;;; C.
2307 ;; [Murmur murmur murmur] Maestro, drum-roll please... [Murmur murmur murmur.]
2308 ;; Ahem. [Murmur murmur murmur] Lay-dees an Gennel-men. [Murmur murmur shhh!]
2309 ;; I am most proud and humbly honoured today [murmur murmur cough] to present
2310 ;; to you good people, the winner of the Second Millennium Award for The Most
2311 ;; Hairy Language Syntax. [Ahhh!] All rise please. [Shuffle shuffle
2312 ;; shuffle.] And a round of applause please. For... The C Language! [Roar.]
2313 ;;
2314 ;; Thank you... You are too kind... It is with a feeling of great privilege
2315 ;; and indeed emotion [sob] that I accept this award. It has been a long hard
2316 ;; road. But we know our destiny. And our future. For we must not rest.
2317 ;; There are more tokens to overload, more shoehorn, more methodologies. But
2318 ;; more is a plus! [Ha ha ha.] And more means plus! [Ho ho ho.] The future
2319 ;; is C++! [Ohhh!] The Third Millennium Award... Will be ours! [Roar.]
2325 "Medium level highlighting for C mode.
2329 "Gaudy level highlighting for C mode.
2336 ;; Type related, but we don't do anything special.
2339 ;; Dan Nicolaescu <done@gnu.org> says this is new.
2353 c-font-lock-extra-types)
2357 )
2360 ;;
2361 ;; These are all anchored at the beginning of line for speed.
2362 ;; Note that `c++-font-lock-keywords-1' depends on `c-font-lock-keywords-1'.
2363 ;;
2364 ;; Fontify function name definitions (GNU style; without type on line).
2366 ;;
2367 ;; Fontify error directives.
2369 ;;
2370 ;; Fontify filenames in #include <...> preprocessor directives as strings.
2373 ;;
2374 ;; Fontify function macro names.
2376 ;;
2377 ;; Fontify symbol names in #elif or #if ... defined preprocessor directives.
2381 ;;
2382 ;; Fontify otherwise as symbol names, and the preprocessor directive names.
2385 ))
2390 ;;
2391 ;; Simple regexps for speed.
2392 ;;
2393 ;; Fontify all type names.
2396 ;;
2397 ;; Fontify all builtin keywords (except case, default and goto; see below).
2399 ;;
2400 ;; Fontify case/goto keywords and targets, and case default/goto tags.
2403 ;; Anders Lindgren <andersl@andersl.com> points out that it is quicker to
2404 ;; use MATCH-ANCHORED to effectively anchor the regexp on the left.
2405 ;; This must come after the one for keywords and targets.
2409 )))
2413 ;;
2414 ;; More complicated regexps for more complete highlighting for types.
2415 ;; We still have to fontify type specifiers individually, as C is so hairy.
2417 ;;
2418 ;; Fontify all storage types, plus their items.
2422 ;; Fontify each declaration item.
2424 ;; Start with point after all type specifiers.
2429 ;; Finish with point after first type specifier.
2431 ;; Fontify as a variable or function name.
2433 font-lock-function-name-face
2434 font-lock-variable-name-face)))))
2435 ;;
2436 ;; Fontify all storage specs and types, plus their items.
2443 nil nil
2444 ;; Fontify as a variable or function name.
2446 font-lock-function-name-face
2448 ;;
2449 ;; Fontify structures, or typedef names, plus their items.
2454 ;;
2455 ;; Fontify anything at beginning of line as a declaration or definition.
2461 font-lock-function-name-face
2462 font-lock-variable-name-face))))
2463 )))
2464 )
2467 "Default expressions to highlight in C mode.
2469 \f
2470 ;;; C++.
2476 "Medium level highlighting for C++ mode.
2480 "Gaudy level highlighting for C++ mode.
2484 ;; Regexp matches after point: word<word>::word (
2485 ;; ^^^^ ^^^^ ^^^^ ^
2486 ;; Where the match subexpressions are: 1 3 5 6
2487 ;;
2488 ;; Item is delimited by (match-beginning 1) and (match-end 1).
2489 ;; If (match-beginning 3) is non-nil, that part of the item incloses a `<>'.
2490 ;; If (match-beginning 5) is non-nil, that part of the item follows a `::'.
2491 ;; If (match-beginning 6) is non-nil, the item is followed by a `('.
2494 ;; Skip any leading whitespace.
2496 ;; This is `c++-type-spec' from below. (Hint hint!)
2500 ;; Match any trailing parenthesis.
2505 ;; Restrict to the end of line, currently guaranteed to be LIMIT.
2508 ;; Move over any item value, etc., to the next item.
2519 "typeid"
2520 ;; Branko Cibej <branko.cibej@hermes.si> says this is new.
2521 "export"
2522 ;; Mark Mitchell <mmitchell@usa.net> says these are new.
2524 ;; Alain Picard <ap@abelard.apana.org.au> suggests treating these
2525 ;; as keywords not types.
2532 ;; Taken from Stroustrup, minus keywords otherwise fontified.
2541 ;; Eric Hopper <hopper@omnifarious.mn.org> says these are new.
2556 ;;
2557 ;; A brave attempt to match templates following a type and/or match
2558 ;; class membership. See and sync the above function
2559 ;; `font-lock-match-c++-style-declaration-item-and-skip-to-next'.
2563 ;; If the string is a type, it may be followed by the cruft above.
2566 ;;
2567 ;; Parenthesis depth of user-defined types not forgetting their cruft.
2570 )
2573 ;;
2574 ;; The list `c-font-lock-keywords-1' less that for function names.
2577 ;;
2578 ;; Fontify function name definitions, possibly incorporating class names.
2581 font-lock-type-face
2582 font-lock-function-name-face))
2585 )))
2590 ;;
2591 ;; The list `c-font-lock-keywords-2' for C++ plus operator overloading.
2595 ;;
2596 ;; Fontify operator overloading.
2600 ;;
2601 ;; Fontify case/goto keywords and targets, and case default/goto tags.
2604 ;; This must come after the one for keywords and targets.
2608 ;;
2609 ;; Fontify other builtin keywords.
2611 ;;
2612 ;; Eric Hopper <hopper@omnifarious.mn.org> says `true' and `false' are new.
2614 )))
2618 ;;
2619 ;; More complicated regexps for more complete highlighting for types.
2621 ;;
2622 ;; Fontify all storage classes and type specifiers, plus their items.
2626 ;; The name of any template type.
2628 ;; Fontify each declaration item.
2630 ;; Start with point after all type specifiers.
2634 ;; Finish with point after first type specifier.
2636 ;; Fontify as a variable or function name.
2638 font-lock-type-face)
2640 font-lock-function-name-face)
2642 font-lock-variable-name-face)))
2645 font-lock-function-name-face
2647 ;;
2648 ;; Fontify all storage specs and types, plus their items.
2652 ;; The name of any template type.
2654 ;; The name of any type.
2657 ;; Fontify each declaration item.
2659 ;; Start with point after all type specifiers.
2660 nil
2661 ;; Finish with point after first type specifier.
2662 nil
2663 ;; Fontify as a variable or function name.
2665 font-lock-type-face)
2667 font-lock-function-name-face)
2669 font-lock-variable-name-face)))
2672 font-lock-function-name-face
2674 ))
2675 ;;
2676 ;; Fontify structures, or typedef names, plus their items.
2681 ;;
2682 ;; Fontify anything at beginning of line as a declaration or definition.
2688 font-lock-type-face)
2693 font-lock-function-name-face
2695 )))
2696 )
2699 "Default expressions to highlight in C++ mode.
2701 \f
2702 ;;; Objective-C.
2708 "Medium level highlighting for Objective-C mode.
2712 "Gaudy level highlighting for Objective-C mode.
2715 ;; Regexps written with help from Stephen Peters <speters@us.oracle.com> and
2716 ;; Jacques Duthen Prestataire <duthen@cegelec-red.fr>.
2738 objc-font-lock-extra-types)
2742 )
2745 ;;
2746 ;; The list `c-font-lock-keywords-1' less that for function names.
2749 ;;
2750 ;; Fontify compiler directives.
2755 ;;
2756 ;; Fontify method names and arguments. Oh Lordy!
2757 ;; First, on the same line as the function declaration.
2762 nil nil
2765 ;; Second, on lines following the function declaration.
2770 )))
2775 ;;
2776 ;; Simple regexps for speed.
2777 ;;
2778 ;; Fontify all type specifiers.
2782 ;;
2783 ;; Fontify all builtin keywords (except case, default and goto; see below).
2785 ;;
2786 ;; Fontify case/goto keywords and targets, and case default/goto tags.
2789 ;; Fontify tags iff sole statement on line, otherwise we detect selectors.
2790 ;; This must come after the one for keywords and targets.
2794 ;;
2795 ;; Fontify null object pointers.
2797 )))
2801 ;;
2802 ;; More complicated regexps for more complete highlighting for types.
2803 ;; We still have to fontify type specifiers individually, as C is so hairy.
2805 ;;
2806 ;; Fontify all storage classes and type specifiers, plus their items.
2810 ;; Fontify each declaration item.
2812 ;; Start with point after all type specifiers.
2817 ;; Finish with point after first type specifier.
2819 ;; Fontify as a variable or function name.
2821 font-lock-function-name-face
2822 font-lock-variable-name-face)))))
2823 ;;
2824 ;; Fontify all storage specs and types, plus their items.
2828 ;; The name of any type.
2830 ;; Fontify each declaration item.
2832 nil nil
2833 ;; Fontify as a variable or function name.
2835 font-lock-function-name-face
2836 font-lock-variable-name-face)))
2837 ))
2838 ;;
2839 ;; Fontify structures, or typedef names, plus their items.
2844 ;;
2845 ;; Fontify anything at beginning of line as a declaration or definition.
2851 font-lock-function-name-face
2852 font-lock-variable-name-face))))
2853 )))
2854 )
2857 "Default expressions to highlight in Objective-C mode.
2859 \f
2860 ;;; Java.
2866 "Medium level highlighting for Java mode.
2870 "Gaudy level highlighting for Java mode.
2873 ;; Regexps written with help from Fred White <fwhite@bbn.com>,
2874 ;; Anders Lindgren <andersl@andersl.com> and Carl Manning <caroma@ai.mit.edu>.
2879 ;; Anders Lindgren <andersl@andersl.com> says these have gone.
2880 ;; "cast" "byvalue" "future" "generic" "operator" "var"
2881 ;; "inner" "outer" "rest"
2884 ;;
2885 ;; Classes immediately followed by an object name.
2892 java-font-lock-extra-types)
2895 ;;
2896 ;; These are eventually followed by an object name.
2901 ;; Anders Lindgren <andersl@andersl.com> says this has gone.
2902 ;; "threadsafe"
2904 ;; Carl Manning <caroma@ai.mit.edu> says this is new.
2906 )
2909 ;;
2910 ;; Fontify class names.
2913 ;;
2914 ;; Fontify package names in import directives.
2920 ))
2925 ;;
2926 ;; Fontify class names.
2930 ;;
2931 ;; Fontify all builtin keywords (except below).
2933 ;;
2934 ;; Fontify keywords and targets, and case default/goto tags.
2937 ;; This must come after the one for keywords and targets.
2941 ;;
2942 ;; Fontify all constants.
2944 ;;
2945 ;; Javadoc tags within comments.
2951 )))
2955 ;;
2956 ;; More complicated regexps for more complete highlighting for types.
2957 ;; We still have to fontify type specifiers individually, as Java is hairy.
2959 ;;
2960 ;; Fontify random types immediately followed by an item or items.
2965 ;; Fontify each declaration item.
2967 ;; Start and finish with point after the type specifier.
2972 ;; Fontify as a variable or function name.
2974 font-lock-function-name-face
2975 font-lock-variable-name-face)))))
2976 ;;
2977 ;; Fontify those that are eventually followed by an item or items.
2982 ;; Fontify each declaration item.
2984 ;; Start with point after all type specifiers.
2986 ;; Finish with point after first type specifier.
2988 ;; Fontify as a variable or function name.
2990 font-lock-function-name-face
2991 font-lock-variable-name-face))))
2992 )))
2993 )
2996 "Default expressions to highlight in Java mode.
2998 \f
2999 ;; Install ourselves:
3004 ;; Provide ourselves:
3008 ;;; font-lock.el ends here