| blob | bb035077f8d856b86c0406ebc5db8a66ab0b39c3 |
1 ;;; font-lock.el --- Electric font lock mode
3 ;; Copyright (C) 1992, 93, 94, 95, 96, 97, 98, 1999, 2000
4 ;; Free Software Foundation, Inc.
6 ;; Author: jwz, then rms, then sm
7 ;; Maintainer: FSF
8 ;; Keywords: languages, faces
10 ;; This file is part of GNU Emacs.
12 ;; GNU Emacs is free software; you can redistribute it and/or modify
13 ;; it under the terms of the GNU General Public License as published by
14 ;; the Free Software Foundation; either version 2, or (at your option)
15 ;; any later version.
17 ;; GNU Emacs is distributed in the hope that it will be useful,
18 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
19 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
20 ;; GNU General Public License for more details.
22 ;; You should have received a copy of the GNU General Public License
23 ;; along with GNU Emacs; see the file COPYING. If not, write to the
24 ;; Free Software Foundation, Inc., 59 Temple Place - Suite 330,
25 ;; Boston, MA 02111-1307, USA.
27 ;;; Commentary:
29 ;; Font Lock mode is a minor mode that causes your comments to be displayed in
30 ;; one face, strings in another, reserved words in another, and so on.
31 ;;
32 ;; Comments will be displayed in `font-lock-comment-face'.
33 ;; Strings will be displayed in `font-lock-string-face'.
34 ;; Regexps are used to display selected patterns in other faces.
35 ;;
36 ;; To make the text you type be fontified, use M-x font-lock-mode RET.
37 ;; When this minor mode is on, the faces of the current line are updated with
38 ;; every insertion or deletion.
39 ;;
40 ;; To turn Font Lock mode on automatically, add this to your ~/.emacs file:
41 ;;
42 ;; (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
43 ;;
44 ;; Or if you want to turn Font Lock mode on in many modes:
45 ;;
46 ;; (global-font-lock-mode t)
47 ;;
48 ;; Fontification for a particular mode may be available in a number of levels
49 ;; of decoration. The higher the level, the more decoration, but the more time
50 ;; it takes to fontify. See the variable `font-lock-maximum-decoration', and
51 ;; also the variable `font-lock-maximum-size'. Support modes for Font Lock
52 ;; mode can be used to speed up Font Lock mode. See `font-lock-support-mode'.
53 \f
54 ;;; How Font Lock mode fontifies:
56 ;; When Font Lock mode is turned on in a buffer, it (a) fontifies the entire
57 ;; buffer and (b) installs one of its fontification functions on one of the
58 ;; hook variables that are run by Emacs after every buffer change (i.e., an
59 ;; insertion or deletion). Fontification means the replacement of `face' text
60 ;; properties in a given region; Emacs displays text with these `face' text
61 ;; properties appropriately.
62 ;;
63 ;; Fontification normally involves syntactic (i.e., strings and comments) and
64 ;; regexp (i.e., keywords and everything else) passes. There are actually
65 ;; three passes; (a) the syntactic keyword pass, (b) the syntactic pass and (c)
66 ;; the keyword pass. Confused?
67 ;;
68 ;; The syntactic keyword pass places `syntax-table' text properties in the
69 ;; buffer according to the variable `font-lock-syntactic-keywords'. It is
70 ;; necessary because Emacs' syntax table is not powerful enough to describe all
71 ;; the different syntactic constructs required by the sort of people who decide
72 ;; that a single quote can be syntactic or not depending on the time of day.
73 ;; (What sort of person could decide to overload the meaning of a quote?)
74 ;; Obviously the syntactic keyword pass must occur before the syntactic pass.
75 ;;
76 ;; The syntactic pass places `face' text properties in the buffer according to
77 ;; syntactic context, i.e., according to the buffer's syntax table and buffer
78 ;; text's `syntax-table' text properties. It involves using a syntax parsing
79 ;; function to determine the context of different parts of a region of text. A
80 ;; syntax parsing function is necessary because generally strings and/or
81 ;; comments can span lines, and so the context of a given region is not
82 ;; necessarily apparent from the content of that region. Because the keyword
83 ;; pass only works within a given region, it is not generally appropriate for
84 ;; syntactic fontification. This is the first fontification pass that makes
85 ;; changes visible to the user; it fontifies strings and comments.
86 ;;
87 ;; The keyword pass places `face' text properties in the buffer according to
88 ;; the variable `font-lock-keywords'. It involves searching for given regexps
89 ;; (or calling given search functions) within the given region. This is the
90 ;; second fontification pass that makes changes visible to the user; it
91 ;; fontifies language reserved words, etc.
92 ;;
93 ;; Oh, and the answer is, "Yes, obviously just about everything should be done
94 ;; in a single syntactic pass, but the only syntactic parser available
95 ;; understands only strings and comments." Perhaps one day someone will write
96 ;; some syntactic parsers for common languages and a son-of-font-lock.el could
97 ;; use them rather then relying so heavily on the keyword (regexp) pass.
99 ;;; How Font Lock mode supports modes or is supported by modes:
101 ;; Modes that support Font Lock mode do so by defining one or more variables
102 ;; whose values specify the fontification. Font Lock mode knows of these
103 ;; variable names from (a) the buffer local variable `font-lock-defaults', if
104 ;; non-nil, or (b) the global variable `font-lock-defaults-alist', if the major
105 ;; mode has an entry. (Font Lock mode is set up via (a) where a mode's
106 ;; patterns are distributed with the mode's package library, and (b) where a
107 ;; mode's patterns are distributed with font-lock.el itself. An example of (a)
108 ;; is Pascal mode, an example of (b) is Lisp mode. Normally, the mechanism is
109 ;; (a); (b) is used where it is not clear which package library should contain
110 ;; the pattern definitions.) Font Lock mode chooses which variable to use for
111 ;; fontification based on `font-lock-maximum-decoration'.
112 ;;
113 ;; Font Lock mode fontification behaviour can be modified in a number of ways.
114 ;; See the below comments and the comments distributed throughout this file.
116 ;;; Constructing patterns:
118 ;; See the documentation for the variable `font-lock-keywords'.
119 ;;
120 ;; Efficient regexps for use as MATCHERs for `font-lock-keywords' and
121 ;; `font-lock-syntactic-keywords' can be generated via the function
122 ;; `regexp-opt'.
124 ;;; Adding patterns for modes that already support Font Lock:
126 ;; Though Font Lock highlighting patterns already exist for many modes, it's
127 ;; likely there's something that you want fontified that currently isn't, even
128 ;; at the maximum fontification level. You can add highlighting patterns via
129 ;; `font-lock-add-keywords'. For example, say in some C
130 ;; header file you #define the token `and' to expand to `&&', etc., to make
131 ;; your C code almost readable. In your ~/.emacs there could be:
132 ;;
133 ;; (font-lock-add-keywords 'c-mode '("\\<\\(and\\|or\\|not\\)\\>"))
134 ;;
135 ;; Some modes provide specific ways to modify patterns based on the values of
136 ;; other variables. For example, additional C types can be specified via the
137 ;; variable `c-font-lock-extra-types'.
139 ;;; Adding patterns for modes that do not support Font Lock:
141 ;; Not all modes support Font Lock mode. If you (as a user of the mode) add
142 ;; patterns for a new mode, you must define in your ~/.emacs a variable or
143 ;; variables that specify regexp fontification. Then, you should indicate to
144 ;; Font Lock mode, via the mode hook setting `font-lock-defaults', exactly what
145 ;; support is required. For example, say Foo mode should have the following
146 ;; regexps fontified case-sensitively, and comments and strings should not be
147 ;; fontified automagically. In your ~/.emacs there could be:
148 ;;
149 ;; (defvar foo-font-lock-keywords
150 ;; '(("\\<\\(one\\|two\\|three\\)\\>" . font-lock-keyword-face)
151 ;; ("\\<\\(four\\|five\\|six\\)\\>" . font-lock-type-face))
152 ;; "Default expressions to highlight in Foo mode.")
153 ;;
154 ;; (add-hook 'foo-mode-hook
155 ;; (function (lambda ()
156 ;; (make-local-variable 'font-lock-defaults)
157 ;; (setq font-lock-defaults '(foo-font-lock-keywords t)))))
159 ;;; Adding Font Lock support for modes:
161 ;; Of course, it would be better that the mode already supports Font Lock mode.
162 ;; The package author would do something similar to above. The mode must
163 ;; define at the top-level a variable or variables that specify regexp
164 ;; fontification. Then, the mode command should indicate to Font Lock mode,
165 ;; via `font-lock-defaults', exactly what support is required. For example,
166 ;; say Bar mode should have the following regexps fontified case-insensitively,
167 ;; and comments and strings should be fontified automagically. In bar.el there
168 ;; could be:
169 ;;
170 ;; (defvar bar-font-lock-keywords
171 ;; '(("\\<\\(uno\\|due\\|tre\\)\\>" . font-lock-keyword-face)
172 ;; ("\\<\\(quattro\\|cinque\\|sei\\)\\>" . font-lock-type-face))
173 ;; "Default expressions to highlight in Bar mode.")
174 ;;
175 ;; and within `bar-mode' there could be:
176 ;;
177 ;; (make-local-variable 'font-lock-defaults)
178 ;; (setq font-lock-defaults '(bar-font-lock-keywords nil t))
179 \f
180 ;; What is fontification for? You might say, "It's to make my code look nice."
181 ;; I think it should be for adding information in the form of cues. These cues
182 ;; should provide you with enough information to both (a) distinguish between
183 ;; different items, and (b) identify the item meanings, without having to read
184 ;; the items and think about it. Therefore, fontification allows you to think
185 ;; less about, say, the structure of code, and more about, say, why the code
186 ;; doesn't work. Or maybe it allows you to think less and drift off to sleep.
187 ;;
188 ;; So, here are my opinions/advice/guidelines:
189 ;;
190 ;; - Highlight conceptual objects, such as function and variable names, and
191 ;; different objects types differently, i.e., (a) and (b) above, highlight
192 ;; function names differently to variable names.
193 ;; - Keep the faces distinct from each other as far as possible.
194 ;; i.e., (a) above.
195 ;; - Use the same face for the same conceptual object, across all modes.
196 ;; i.e., (b) above, all modes that have items that can be thought of as, say,
197 ;; keywords, should be highlighted with the same face, etc.
198 ;; - Make the face attributes fit the concept as far as possible.
199 ;; i.e., function names might be a bold colour such as blue, comments might
200 ;; be a bright colour such as red, character strings might be brown, because,
201 ;; err, strings are brown (that was not the reason, please believe me).
202 ;; - Don't use a non-nil OVERRIDE unless you have a good reason.
203 ;; Only use OVERRIDE for special things that are easy to define, such as the
204 ;; way `...' quotes are treated in strings and comments in Emacs Lisp mode.
205 ;; Don't use it to, say, highlight keywords in commented out code or strings.
206 ;; - Err, that's it.
207 \f
208 ;;; Code:
210 ;; Define core `font-lock' group.
212 "Font Lock mode text highlighting package."
218 "Faces for highlighting text."
223 "Extra mode-specific type names for highlighting declarations."
226 ;; Define support mode groups here to impose `font-lock' group order.
228 "Font Lock support mode to cache fontification."
234 "Font Lock support mode to fontify lazily."
240 "Font Lock support mode to fontify just-in-time."
245 \f
246 ;; User variables.
249 "*Maximum size of a buffer for buffer fontification.
250 Only buffers less than this can be fontified when Font Lock mode is turned on.
251 If nil, means size is irrelevant.
252 If a list, each element should be a cons pair of the form (MAJOR-MODE . SIZE),
253 where MAJOR-MODE is a symbol or t (meaning the default). For example:
254 ((c-mode . 256000) (c++-mode . 256000) (rmail-mode . 1048576))
255 means that the maximum size is 250K for buffers in C or C++ modes, one megabyte
256 for buffers in Rmail mode, and size is irrelevant otherwise."
271 "*Maximum decoration level for fontification.
272 If nil, use the default decoration (typically the minimum available).
273 If t, use the maximum decoration available.
274 If a number, use that level of decoration (or if not available the maximum).
275 If a list, each element should be a cons pair of the form (MAJOR-MODE . LEVEL),
276 where MAJOR-MODE is a symbol or t (meaning the default). For example:
277 ((c-mode . t) (c++-mode . 2) (t . 1))
278 means use the maximum decoration available for buffers in C mode, level 2
279 decoration for buffers in C++ mode, and level 1 decoration otherwise."
296 "*If non-nil, means show status messages for buffer fontification.
297 If a number, only buffers greater than this size have fontification messages."
302 \f
303 ;; Fontification variables:
306 "A list of the keywords to highlight.
307 Each element should have one of these forms:
309 MATCHER
310 (MATCHER . MATCH)
311 (MATCHER . FACENAME)
312 (MATCHER . HIGHLIGHT)
313 (MATCHER HIGHLIGHT ...)
314 (eval . FORM)
316 where HIGHLIGHT should be either MATCH-HIGHLIGHT or MATCH-ANCHORED.
318 FORM is an expression, whose value should be a keyword element, evaluated when
319 the keyword is (first) used in a buffer. This feature can be used to provide a
320 keyword that can only be generated when Font Lock mode is actually turned on.
323 typically only MATCH-HIGHLIGHT is required.
324 However, if an item or (typically) items are to be highlighted following the
325 instance of another item (the anchor), for example each instance of the
328 MATCH-HIGHLIGHT should be of the form:
330 (MATCH FACENAME OVERRIDE LAXMATCH)
332 where MATCHER can be either the regexp to search for, or the function name to
333 call to make the search (called with one argument, the limit of the search) and
334 return non-nil if it succeeds (and set `match-data' appropriately).
335 MATCHER regexps can be generated via the function `regexp-opt'. MATCH is
336 the subexpression of MATCHER to be highlighted. FACENAME is an expression
337 whose value is the face name to use. Face default attributes can be
340 OVERRIDE and LAXMATCH are flags. If OVERRIDE is t, existing fontification can
341 be overwritten. If `keep', only parts not already fontified are highlighted.
342 If `prepend' or `append', existing fontification is merged with the new, in
343 which the new or existing fontification, respectively, takes precedence.
344 If LAXMATCH is non-nil, no error is signaled if there is no MATCH in MATCHER.
346 For example, an element of the form highlights (if not already highlighted):
349 variable `font-lock-keyword-face'.
351 the value of `font-lock-keyword-face'.
355 of `foo-bar-face', even if already highlighted.
356 (fubar-match 1 fubar-face)
357 the first subexpression within all occurrences of
358 whatever the function `fubar-match' finds and matches
359 in the value of `fubar-face'.
361 MATCH-ANCHORED should be of the form:
363 (MATCHER PRE-MATCH-FORM POST-MATCH-FORM MATCH-HIGHLIGHT ...)
365 where MATCHER is a regexp to search for or the function name to call to make
366 the search, as for MATCH-HIGHLIGHT above, but with one exception; see below.
367 PRE-MATCH-FORM and POST-MATCH-FORM are evaluated before the first, and after
368 the last, instance MATCH-ANCHORED's MATCHER is used. Therefore they can be
369 used to initialise before, and cleanup after, MATCHER is used. Typically,
370 PRE-MATCH-FORM is used to move to some position relative to the original
371 MATCHER, before starting with MATCH-ANCHORED's MATCHER. POST-MATCH-FORM might
372 be used to move, before resuming with MATCH-ANCHORED's parent's MATCHER.
374 For example, an element of the form highlights (if not already highlighted):
385 The above-mentioned exception is as follows. The limit of the MATCHER search
386 defaults to the end of the line after PRE-MATCH-FORM is evaluated.
387 However, if PRE-MATCH-FORM returns a position greater than the position after
388 PRE-MATCH-FORM is evaluated, that position is used as the limit of the search.
389 It is generally a bad idea to return a position greater than the end of the
390 line, i.e., cause the MATCHER search to span lines.
392 These regular expressions can match text which spans lines, although
393 it is better to avoid it if possible since updating them while editing
394 text is slower, and it is not guaranteed to be always correct when using
395 support modes like jit-lock or lazy-lock.
397 This variable is set by major modes via the variable `font-lock-defaults'.
398 Be careful when composing regexps for this list; a poorly written pattern can
401 ;; This variable is used by mode packages that support Font Lock mode by
402 ;; defining their own keywords to use for `font-lock-keywords'. (The mode
403 ;; command should make it buffer-local and set it to provide the set up.)
405 "Defaults for Font Lock mode specified by the major mode.
406 Defaults should be of the form:
408 (KEYWORDS KEYWORDS-ONLY CASE-FOLD SYNTAX-ALIST SYNTAX-BEGIN ...)
410 KEYWORDS may be a symbol (a variable or function whose value is the keywords to
411 use for fontification) or a list of symbols. If KEYWORDS-ONLY is non-nil,
412 syntactic fontification (strings and comments) is not performed.
413 If CASE-FOLD is non-nil, the case of the keywords is ignored when fontifying.
414 If SYNTAX-ALIST is non-nil, it should be a list of cons pairs of the form
415 \(CHAR-OR-STRING . STRING) used to set the local Font Lock syntax table, for
416 keyword and syntactic fontification (see `modify-syntax-entry').
418 If SYNTAX-BEGIN is non-nil, it should be a function with no args used to move
419 backwards outside any enclosing syntactic block, for syntactic fontification.
420 Typical values are `beginning-of-line' (i.e., the start of the line is known to
421 be outside a syntactic block), or `beginning-of-defun' for programming modes or
422 `backward-paragraph' for textual modes (i.e., the mode-dependent function is
423 known to move outside a syntactic block). If nil, the beginning of the buffer
424 is used as a position outside of a syntactic block, in the worst case.
426 These item elements are used by Font Lock mode to set the variables
427 `font-lock-keywords', `font-lock-keywords-only',
428 `font-lock-keywords-case-fold-search', `font-lock-syntax-table' and
429 `font-lock-beginning-of-syntax-function', respectively.
431 Further item elements are alists of the form (VARIABLE . VALUE) and are in no
432 particular order. Each VARIABLE is made buffer-local before set to VALUE.
434 Currently, appropriate variables include `font-lock-mark-block-function'.
435 If this is non-nil, it should be a function with no args used to mark any
437 Typical values are `mark-defun' for programming modes or `mark-paragraph' for
438 textual modes (i.e., the mode-dependent function is known to put point and mark
439 around a text block relevant to that mode).
441 Other variables include that for syntactic keyword fontification,
442 `font-lock-syntactic-keywords'
443 and those for buffer-specialised fontification functions,
444 `font-lock-fontify-buffer-function', `font-lock-unfontify-buffer-function',
445 `font-lock-fontify-region-function', `font-lock-unfontify-region-function',
448 ;; This variable is used where font-lock.el itself supplies the keywords.
451 ;; Thus the calculation of the cache is usually faster but not
452 ;; infallible, so we risk mis-fontification. sm.
455 c-font-lock-keywords-2 c-font-lock-keywords-3)
465 objc-font-lock-keywords-2 objc-font-lock-keywords-3)
470 java-font-lock-keywords-2 java-font-lock-keywords-3)
475 lisp-font-lock-keywords-1 lisp-font-lock-keywords-2)
478 ;; For TeX modes we could use `backward-paragraph' for the same reason.
479 ;; But we don't, because paragraph breaks are arguably likely enough to
480 ;; occur within a genuine syntactic block to make it too risky.
481 ;; However, we do specify a MARK-BLOCK function as that cannot result
482 ;; in a mis-fontification even if it might not fontify enough. sm.
485 tex-font-lock-keywords-1 tex-font-lock-keywords-2)
488 )
501 "Alist of fall-back Font Lock defaults for major modes.
502 Each item should be a list of the form:
504 (MAJOR-MODE . FONT-LOCK-DEFAULTS)
506 where MAJOR-MODE is a symbol and FONT-LOCK-DEFAULTS is a list of default
510 "*Alist of `font-lock-keywords' local to a `major-mode'.
511 This is normally set via `font-lock-add-keywords' and
515 "*Alist of `font-lock-keywords' removed from `major-mode'.
516 This is normally set via `font-lock-add-keywords' and
520 "*Non-nil means Font Lock should not fontify comments or strings.
524 "*Non-nil means the patterns in `font-lock-keywords' are case-insensitive.
528 "A list of the syntactic keywords to highlight.
529 Can be the list or the name of a function or variable whose value is the list.
530 See `font-lock-keywords' for a description of the form of this list;
531 the differences are listed below. MATCH-HIGHLIGHT should be of the form:
533 (MATCH SYNTAX OVERRIDE LAXMATCH)
535 where SYNTAX can be of the form (SYNTAX-CODE . MATCHING-CHAR) (see
536 also `string-to-syntax'), the name of a syntax table, or an expression
537 whose value is such a form or a syntax table. OVERRIDE cannot be
538 `prepend' or `append'.
540 For example, an element of the form highlights syntactically:
544 a hash character when following a dollar character, with a SYNTAX-CODE of
545 1 (meaning punctuation syntax). Assuming that the buffer syntax table does
546 specify hash characters to have comment start syntax, the element will only
547 highlight hash characters that do not follow dollar characters as comments
548 syntactically.
551 (1 (7 . ?'))
552 (2 (7 . ?')))
554 both single quotes which surround a single character, with a SYNTAX-CODE of
555 7 (meaning string quote syntax) and a MATCHING-CHAR of a single quote (meaning
556 a single quote matches a single quote). Assuming that the buffer syntax table
557 does not specify single quotes to have quote syntax, the element will only
558 highlight single quotes of the form 'c' as strings syntactically.
559 Other forms, such as foo'bar or 'fubar', will not be highlighted as strings.
564 "Non-nil means use this syntax table for fontifying.
565 If this is nil, the major mode's syntax table is used.
568 ;; If this is nil, we only use the beginning of the buffer if we can't use
569 ;; `font-lock-cache-position' and `font-lock-cache-state'.
571 "*Non-nil means use this function to move back outside of a syntactic block.
572 When called with no args it should leave point at the beginning of any
573 enclosing syntactic block.
574 If this is nil, the beginning of the buffer is used (in the worst case).
578 "*Non-nil means use this function to mark a block of text.
579 When called with no args it should leave point at the beginning of any
580 enclosing textual block and mark at the end.
584 "Function to use for fontifying the buffer.
588 "Function to use for unfontifying the buffer.
589 This is used when turning off Font Lock mode.
593 "Function to use for fontifying a region.
594 It should take two args, the beginning and end of the region, and an optional
595 third arg VERBOSE. If non-nil, the function should print status messages.
599 "Function to use for unfontifying a region.
600 It should take two args, the beginning and end of the region.
604 "List of Font Lock mode related modes that should not be turned on.
605 Currently, valid mode names are `fast-lock-mode', `jit-lock-mode' and
609 "Whether font-lock should cater to multiline keywords.
610 If nil, don't try to handle multiline patterns.
611 If t, always handle multiline patterns.
612 If `undecided', don't try to handle multiline patterns until you see one.
618 ;;;###autoload
621 \f
622 ;; Font Lock mode.
625 ;;
626 ;; We don't do this at the top-level as we only use non-autoloaded macros.
628 ;;
629 ;; Borrowed from lazy-lock.el.
630 ;; We use this to preserve or protect things when modifying text properties.
632 "Bind variables according to VARLIST and eval BODY restoring buffer state."
636 before-change-functions after-change-functions
637 deactivate-mark buffer-file-name buffer-file-truename))
638 ,@body
643 ;;
644 ;; Shut up the byte compiler.
650 ;;;###autoload
652 "Toggle Font Lock mode.
653 With arg, turn Font Lock mode on if and only if arg is positive.
655 When Font Lock mode is enabled, text is fontified as you type it:
657 - Comments are displayed in `font-lock-comment-face';
658 - Strings are displayed in `font-lock-string-face';
659 - Certain other expressions are displayed in other faces according to the
660 value of the variable `font-lock-keywords'.
662 You can enable Font Lock mode in any major mode automatically by turning on in
663 the major mode's hook. For example, put in your ~/.emacs:
665 (add-hook 'c-mode-hook 'turn-on-font-lock)
667 Alternatively, you can use Global Font Lock mode to automagically turn on Font
668 Lock mode in buffers whose major mode supports it and whose major mode is one
669 of `font-lock-global-modes'. For example, put in your ~/.emacs:
671 (global-font-lock-mode t)
673 There are a number of support modes that may be used to speed up Font Lock mode
674 in various ways, specified via the variable `font-lock-support-mode'. Where
675 major modes support different levels of fontification, you can use the variable
676 `font-lock-maximum-decoration' to specify which level you generally prefer.
677 When you turn Font Lock mode on/off the buffer is fontified/defontified, though
678 fontification occurs only if the buffer is less than `font-lock-maximum-size'.
680 For example, to specify that Font Lock mode use use Lazy Lock mode as a support
681 mode and use maximum levels of fontification, put in your ~/.emacs:
683 (setq font-lock-support-mode 'lazy-lock-mode)
684 (setq font-lock-maximum-decoration t)
686 To add your own highlighting for some major mode, and modify the highlighting
687 selected automatically via the variable `font-lock-maximum-decoration', you can
688 use `font-lock-add-keywords'.
690 To fontify a buffer, without turning on Font Lock mode and regardless of buffer
693 To fontify a block (the function or paragraph containing point, or a number of
694 lines around point), perhaps because modification on the current line caused
697 See the variable `font-lock-defaults-alist' for the Font Lock mode default
698 settings. You can set your own default settings for some mode, by setting a
699 buffer local value for `font-lock-defaults', via its mode hook."
701 ;; Don't turn on Font Lock mode if we don't have a display (we're running a
702 ;; batch job) or if the buffer is invisible (the name starts with a space).
709 ;; Turn on Font Lock mode.
716 ;; Fontify the buffer if we have to.
719 nil)
725 ;; Turn off Font Lock mode.
733 ;;;###autoload
735 "Turn on Font Lock mode conditionally.
736 Turn on only if the terminal can display it."
740 ;;;###autoload
742 "Add highlighting KEYWORDS for MODE.
743 MODE should be a symbol, the major mode command name, such as `c-mode'
744 or nil. If nil, highlighting keywords are added for the current buffer.
745 KEYWORDS should be a list; see the variable `font-lock-keywords'.
746 By default they are added at the beginning of the current highlighting list.
747 If optional argument APPEND is `set', they are used to replace the current
748 highlighting list. If APPEND is any other non-nil value, they are added at the
749 end of the current highlighting list.
751 For example:
753 (font-lock-add-keywords 'c-mode
757 adds two fontification patterns for C mode, to fontify `FIXME:' words, even in
758 comments, and to fontify `and', `or' and `not' words as keywords.
760 Note that some modes have specialised support for additional patterns, e.g.,
761 see the variables `c-font-lock-extra-types', `c++-font-lock-extra-types',
762 `objc-font-lock-extra-types' and `java-font-lock-extra-types'."
764 ;; If MODE is non-nil, add the KEYWORDS and APPEND spec to
765 ;; `font-lock-keywords-alist' so `font-lock-set-defaults' uses them.
772 ;; Make sure that `font-lock-removed-keywords-alist' does not
773 ;; contain the new keywords.
776 ;; Otherwise set or add the keywords now.
783 font-lock-keywords)))
789 ;; Update `font-lock-removed-keywords-alist' when adding new
790 ;; KEYWORDS to MODE.
791 ;;
792 ;; When font-lock is enabled first all keywords in the list
793 ;; `font-lock-keywords-alist' are added, then all keywords in the
794 ;; list `font-lock-removed-keywords-alist' are removed. If a
795 ;; keyword was once added, removed, and then added again it must be
796 ;; removed from the removed-keywords list. Otherwise the second add
797 ;; will not take effect.
801 ;; A new set of keywords is defined. Forget all about
802 ;; our old keywords that should be removed.
805 ;; Delete all previously removed keywords.
808 ;; Delete the mode cell if empty.
813 ;; Written by Anders Lindgren <andersl@andersl.com>.
814 ;;
815 ;; Case study:
816 ;; (I) The keywords are removed from a major mode.
817 ;; In this case the keyword could be local (i.e. added earlier by
818 ;; `font-lock-add-keywords'), global, or both.
819 ;;
820 ;; (a) In the local case we remove the keywords from the variable
821 ;; `font-lock-keywords-alist'.
822 ;;
823 ;; (b) The actual global keywords are not known at this time.
824 ;; All keywords are added to `font-lock-removed-keywords-alist',
825 ;; when font-lock is enabled those keywords are removed.
826 ;;
827 ;; Note that added keywords are taken out of the list of removed
828 ;; keywords. This ensure correct operation when the same keyword
829 ;; is added and removed several times.
830 ;;
831 ;; (II) The keywords are removed from the current buffer.
832 ;;;###autoload
834 "Remove highlighting KEYWORDS for MODE.
836 MODE should be a symbol, the major mode command name, such as `c-mode'
837 or nil. If nil, highlighting keywords are removed for the current buffer."
839 ;; Remove one keyword at the time.
842 ;; If MODE is non-nil, remove the KEYWORD from
843 ;; `font-lock-keywords-alist'.
846 ;; `keywords-list-append-pair' is a cons with a list of
847 ;; keywords in the car top-cell and the original append
848 ;; argument in the cdr top-cell.
851 ;; Remove keyword list/append pair when the keyword list
852 ;; is empty and append doesn't specify `set'. (If it
853 ;; should be deleted then previously deleted keywords
854 ;; would appear again.)
861 ;; Final cleanup, remove major mode cell if last keyword
862 ;; was deleted.
866 ;; Remember the keyword in case it is not local.
872 font-lock-removed-keywords-alist))))))
874 ;; Otherwise remove it immediately.
880 ;; The keywords might be compiled.
882 font-lock-keywords)))))))
883 \f
884 ;;; Global Font Lock mode.
886 ;; A few people have hassled in the past for a way to make it easier to turn on
887 ;; Font Lock mode, without the user needing to know for which modes s/he has to
888 ;; turn it on, perhaps the same way hilit19.el/hl319.el does. I've always
889 ;; balked at that way, as I see it as just re-moulding the same problem in
890 ;; another form. That is; some person would still have to keep track of which
891 ;; modes (which may not even be distributed with Emacs) support Font Lock mode.
892 ;; The list would always be out of date. And that person might have to be me.
894 ;; Implementation.
895 ;;
896 ;; In a previous discussion the following hack came to mind. It is a gross
897 ;; hack, but it generally works. We use the convention that major modes start
898 ;; by calling the function `kill-all-local-variables', which in turn runs
899 ;; functions on the hook variable `change-major-mode-hook'. We attach our
900 ;; function `font-lock-change-major-mode' to that hook. Of course, when this
901 ;; hook is run, the major mode is in the process of being changed and we do not
902 ;; know what the final major mode will be. So, `font-lock-change-major-mode'
903 ;; only (a) notes the name of the current buffer, and (b) adds our function
904 ;; `turn-on-font-lock-if-enabled' to the hook variables `find-file-hooks' and
905 ;; `post-command-hook' (for buffers that are not visiting files). By the time
906 ;; the functions on the first of these hooks to be run are run, the new major
907 ;; mode is assumed to be in place. This way we get a Font Lock function run
908 ;; when a major mode is turned on, without knowing major modes or their hooks.
909 ;;
910 ;; Naturally this requires that (a) major modes run `kill-all-local-variables',
911 ;; as they are supposed to do, and (b) the major mode is in place after the
912 ;; file is visited or the command that ran `kill-all-local-variables' has
913 ;; finished, whichever the sooner. Arguably, any major mode that does not
914 ;; follow the convension (a) is broken, and I can't think of any reason why (b)
915 ;; would not be met (except `gnudoit' on non-files). However, it is not clean.
916 ;;
917 ;; Probably the cleanest solution is to have each major mode function run some
918 ;; hook, e.g., `major-mode-hook', but maybe implementing that change is
919 ;; impractical. I am personally against making `setq' a macro or be advised,
920 ;; or have a special function such as `set-major-mode', but maybe someone can
921 ;; come up with another solution?
923 ;; User interface.
924 ;;
925 ;; Although Global Font Lock mode is a pseudo-mode, I think that the user
926 ;; interface should conform to the usual Emacs convention for modes, i.e., a
927 ;; command to toggle the feature (`global-font-lock-mode') with a variable for
928 ;; finer control of the mode's behaviour (`font-lock-global-modes').
929 ;;
930 ;; The feature should not be enabled by loading font-lock.el, since other
931 ;; mechanisms for turning on Font Lock mode, such as M-x font-lock-mode RET or
932 ;; (add-hook 'c-mode-hook 'turn-on-font-lock), would cause Font Lock mode to be
933 ;; turned on everywhere. That would not be intuitive or informative because
934 ;; loading a file tells you nothing about the feature or how to control it. It
935 ;; would also be contrary to the Principle of Least Surprise. sm.
939 ;;;###autoload
941 "Toggle Global Font Lock mode.
942 With prefix ARG, turn Global Font Lock mode on if and only if ARG is positive.
943 Displays a message saying whether the mode is on or off if MESSAGE is non-nil.
944 Returns the new status of Global Font Lock mode (non-nil means on).
946 When Global Font Lock mode is enabled, Font Lock mode is automagically
947 turned on in a buffer if its major mode is one of `font-lock-global-modes'."
967 ;; This variable was originally a `defvar' to keep track of
968 ;; whether Global Font Lock mode was turned on or not. As a `defcustom' with
969 ;; special `:set' and `:require' forms, we can provide custom mode control.
970 ;;;###autoload
972 "Toggle Global Font Lock mode.
973 When Global Font Lock mode is enabled, Font Lock mode is automagically
974 turned on in a buffer if its major mode is one of `font-lock-global-modes'.
975 Setting this variable directly does not take effect;
985 "*Modes for which Font Lock mode is automagically turned on.
986 Global Font Lock mode is controlled by the command `global-font-lock-mode'.
987 If nil, means no modes have Font Lock mode automatically turned on.
988 If t, all modes that support Font Lock mode have it automatically turned on.
989 If a list, it should be a list of `major-mode' symbol names for which Font Lock
990 mode should be automatically turned on. The sense of the list is negated if it
991 begins with `not'. For example:
992 (c-mode c++-mode)
993 means that Font Lock mode is turned on for buffers in C and C++ modes only."
1003 ;; Turn off Font Lock mode if it's on.
1006 ;; Gross hack warning: Delicate readers should avert eyes now.
1007 ;; Something is running `kill-all-local-variables', which generally means the
1008 ;; major mode is being changed. Run `turn-on-font-lock-if-enabled' after the
1009 ;; file is visited or the current command has finished.
1015 ;; Gross hack warning: Delicate readers should avert eyes now.
1016 ;; Turn on Font Lock mode if it's supported by the major mode and enabled by
1017 ;; the user.
1035 ;;; End of Global Font Lock mode.
1036 \f
1037 ;;; Font Lock Support mode.
1039 ;; This is the code used to interface font-lock.el with any of its add-on
1040 ;; packages, and provide the user interface. Packages that have their own
1041 ;; local buffer fontification functions (see below) may have to call
1042 ;; `font-lock-after-fontify-buffer' and/or `font-lock-after-unfontify-buffer'
1043 ;; themselves.
1046 "*Support mode for Font Lock mode.
1047 Support modes speed up Font Lock mode by being choosy about when fontification
1048 occurs. Known support modes are Fast Lock mode (symbol `fast-lock-mode'),
1049 Lazy Lock mode (symbol `lazy-lock-mode'), and Just-in-time Lock mode (symbol
1050 `jit-lock-mode'. See those modes for more info.
1051 If nil, means support for Font Lock mode is never performed.
1052 If a symbol, use that support mode.
1053 If a list, each element should be of the form (MAJOR-MODE . SUPPORT-MODE),
1054 where MAJOR-MODE is a symbol or t (meaning the default). For example:
1055 ((c-mode . fast-lock-mode) (c++-mode . fast-lock-mode) (t . lazy-lock-mode))
1056 means that Fast Lock mode is used to support Font Lock mode for buffers in C or
1057 C++ modes, and Lazy Lock mode is used to support Font Lock mode otherwise.
1059 The value of this variable is used when Font Lock mode is turned on."
1075 ))
1103 ;; Useless now that jit-lock intercepts font-lock-fontify-buffer. -sm
1104 ;; (jit-lock-mode
1105 ;; (jit-lock-after-fontify-buffer))
1112 ;; Useless as well. It's only called when:
1113 ;; - turning off font-lock: it does not matter if we leave spurious
1114 ;; `fontified' text props around since jit-lock-mode is also off.
1115 ;; - font-lock-default-fontify-buffer fails: this is not run
1116 ;; any more anyway. -sm
1117 ;;
1118 ;; (jit-lock-mode
1119 ;; (jit-lock-after-unfontify-buffer))
1123 ;;; End of Font Lock Support mode.
1124 \f
1125 ;;; Fontification functions.
1127 ;; Rather than the function, e.g., `font-lock-fontify-region' containing the
1128 ;; code to fontify a region, the function runs the function whose name is the
1129 ;; value of the variable, e.g., `font-lock-fontify-region-function'. Normally,
1130 ;; the value of this variable is, e.g., `font-lock-default-fontify-region'
1131 ;; which does contain the code to fontify a region. However, the value of the
1132 ;; variable could be anything and thus, e.g., `font-lock-fontify-region' could
1133 ;; do anything. The indirection of the fontification functions gives major
1134 ;; modes the capability of modifying the way font-lock.el fontifies. Major
1135 ;; modes can modify the values of, e.g., `font-lock-fontify-region-function',
1136 ;; via the variable `font-lock-defaults'.
1137 ;;
1138 ;; For example, Rmail mode sets the variable `font-lock-defaults' so that
1139 ;; font-lock.el uses its own function for buffer fontification. This function
1140 ;; makes fontification be on a message-by-message basis and so visiting an
1141 ;; RMAIL file is much faster. A clever implementation of the function might
1142 ;; fontify the headers differently than the message body. (It should, and
1143 ;; correspondingly for Mail mode, but I can't be bothered to do the work. Can
1144 ;; you?) This hints at a more interesting use...
1145 ;;
1146 ;; Languages that contain text normally contained in different major modes
1147 ;; could define their own fontification functions that treat text differently
1148 ;; depending on its context. For example, Perl mode could arrange that here
1149 ;; docs are fontified differently than Perl code. Or Yacc mode could fontify
1150 ;; rules one way and C code another. Neat!
1151 ;;
1152 ;; A further reason to use the fontification indirection feature is when the
1153 ;; default syntactual fontification, or the default fontification in general,
1154 ;; is not flexible enough for a particular major mode. For example, perhaps
1155 ;; comments are just too hairy for `font-lock-fontify-syntactically-region' to
1156 ;; cope with. You need to write your own version of that function, e.g.,
1157 ;; `hairy-fontify-syntactically-region', and make your own version of
1158 ;; `hairy-fontify-region' call that function before calling
1159 ;; `font-lock-fontify-keywords-region' for the normal regexp fontification
1160 ;; pass. And Hairy mode would set `font-lock-defaults' so that font-lock.el
1161 ;; would call your region fontification function instead of its own. For
1162 ;; example, TeX modes could fontify {\foo ...} and \bar{...} etc. multi-line
1163 ;; directives correctly and cleanly. (It is the same problem as fontifying
1164 ;; multi-line strings and comments; regexps are not appropriate for the job.)
1166 ;;;###autoload
1168 "Fontify the current buffer the way the function `font-lock-mode' would."
1185 font-lock-verbose)))
1189 ;; Make sure we have the right `font-lock-keywords' etc.
1192 ;; Make sure we fontify etc. in the whole buffer.
1201 ;; We don't restore the old fontification, so it's best to unfontify.
1203 ;; Make sure we undo `font-lock-keywords' etc.
1208 ;; Make sure we unfontify etc. in the whole buffer.
1222 ;; Use the fontification syntax table, if any.
1225 ;; check to see if we should expand the beg/end area for
1226 ;; proper multiline matches
1228 ;; if the text-property is non-nil, (1+ beg)
1229 ;; is valid. We need to use (1+ beg) for the
1230 ;; case where (get-text-property (1- beg)) is nil
1231 ;; in which case we want to keep BEG but
1232 ;; previous-single-property-change will return
1233 ;; the previous change (if any) rather than
1234 ;; the one at BEG.
1238 beg))
1242 ;; Now do the fontification.
1249 ;; Clean up.
1252 ;; The following must be rethought, since keywords can override fontification.
1253 ; ;; Now scan for keywords, but not if we are inside a comment now.
1254 ; (or (and (not font-lock-keywords-only)
1255 ; (let ((state (parse-partial-sexp beg end nil nil
1256 ; font-lock-cache-state)))
1257 ; (or (nth 4 state) (nth 7 state))))
1258 ; (font-lock-fontify-keywords-region beg end))
1267 ;; Called when any modification is made to buffer text.
1272 ;; Rescan between start of lines enclosing the region.
1278 "Fontify some lines the way `font-lock-fontify-buffer' would.
1279 The lines could be a function or paragraph, or a specified number of lines.
1280 If ARG is given, fontify that many lines before and after point, or 16 lines if
1281 no ARG is given and `font-lock-mark-block-function' is nil.
1282 If `font-lock-mark-block-function' non-nil and no ARG is given, it is used to
1283 delimit the region to fontify."
1286 deactivate-mark)
1287 ;; Make sure we have the right `font-lock-keywords' etc.
1303 ;;; End of Fontification functions.
1304 \f
1305 ;;; Additional text property functions.
1307 ;; The following text property functions should be builtins. This means they
1308 ;; should be written in C and put with all the other text property functions.
1309 ;; In the meantime, those that are used by font-lock.el are defined in Lisp
1310 ;; below and given a `font-lock-' prefix. Those that are not used are defined
1311 ;; in Lisp below and commented out. sm.
1314 "Prepend to one property of the text from START to END.
1315 Arguments PROP and VALUE specify the property and value to prepend to the value
1316 already in place. The resulting property values are always lists.
1317 Optional argument OBJECT is the string or buffer containing the text."
1324 object)
1328 "Append to one property of the text from START to END.
1329 Arguments PROP and VALUE specify the property and value to append to the value
1330 already in place. The resulting property values are always lists.
1331 Optional argument OBJECT is the string or buffer containing the text."
1338 object)
1342 "Fill in one property of the text from START to END.
1343 Arguments PROP and VALUE specify the property and value to put where none are
1344 already in place. Therefore existing property values are not overwritten.
1345 Optional argument OBJECT is the string or buffer containing the text."
1352 ;; For completeness: this is to `remove-text-properties' as `put-text-property'
1353 ;; is to `add-text-properties', etc.
1354 ;(defun remove-text-property (start end property &optional object)
1355 ; "Remove a property from text from START to END.
1356 ;Argument PROPERTY is the property to remove.
1357 ;Optional argument OBJECT is the string or buffer containing the text.
1358 ;Return t if the property was actually removed, nil otherwise."
1359 ; (remove-text-properties start end (list property) object))
1361 ;; For consistency: maybe this should be called `remove-single-property' like
1362 ;; `next-single-property-change' (not `next-single-text-property-change'), etc.
1363 ;(defun remove-single-text-property (start end prop value &optional object)
1364 ; "Remove a specific property value from text from START to END.
1365 ;Arguments PROP and VALUE specify the property and value to remove. The
1366 ;resulting property values are not equal to VALUE nor lists containing VALUE.
1367 ;Optional argument OBJECT is the string or buffer containing the text."
1368 ; (let ((start (text-property-not-all start end prop nil object)) next prev)
1369 ; (while start
1370 ; (setq next (next-single-property-change start prop object end)
1371 ; prev (get-text-property start prop object))
1372 ; (cond ((and (symbolp prev) (eq value prev))
1373 ; (remove-text-property start next prop object))
1374 ; ((and (listp prev) (memq value prev))
1375 ; (let ((new (delq value prev)))
1376 ; (cond ((null new)
1377 ; (remove-text-property start next prop object))
1378 ; ((= (length new) 1)
1379 ; (put-text-property start next prop (car new) object))
1380 ; (t
1381 ; (put-text-property start next prop new object))))))
1382 ; (setq start (text-property-not-all next end prop nil object)))))
1384 ;;; End of Additional text property functions.
1385 \f
1386 ;;; Syntactic regexp fontification functions.
1388 ;; These syntactic keyword pass functions are identical to those keyword pass
1389 ;; functions below, with the following exceptions; (a) they operate on
1390 ;; `font-lock-syntactic-keywords' of course, (b) they are all `defun' as speed
1391 ;; is less of an issue, (c) eval of property value does not occur JIT as speed
1392 ;; is less of an issue, (d) OVERRIDE cannot be `prepend' or `append' as it
1393 ;; makes no sense for `syntax-table' property values, (e) they do not do it
1394 ;; LOUDLY as it is not likely to be intensive.
1397 "Apply HIGHLIGHT following a match.
1398 HIGHLIGHT should be of the form MATCH-HIGHLIGHT,
1399 see `font-lock-syntactic-keywords'."
1409 ;; No match but we might not signal an error.
1413 ;; Cannot override existing fontification.
1417 ;; Override existing fontification.
1420 ;; Keep existing fontification.
1424 "Fontify according to KEYWORDS until LIMIT.
1425 KEYWORDS should be of the form MATCH-ANCHORED, see `font-lock-keywords',
1426 LIMIT can be modified by the value of its PRE-MATCH-FORM."
1428 ;; Evaluate PRE-MATCH-FORM.
1430 ;; Set LIMIT to value of PRE-MATCH-FORM or the end of line.
1435 ;; Find an occurrence of `matcher' before `limit'.
1439 ;; Apply each highlight to this instance of `matcher'.
1444 ;; Evaluate POST-MATCH-FORM.
1448 "Fontify according to `font-lock-syntactic-keywords' between START and END.
1449 START should be at the beginning of a line."
1450 ;; If `font-lock-syntactic-keywords' is a symbol, get the real keywords.
1453 font-lock-syntactic-keywords)))
1454 ;; If `font-lock-syntactic-keywords' is not compiled, compile it.
1457 font-lock-syntactic-keywords)))
1458 ;; Get down to business.
1461 keyword matcher highlights)
1463 ;; Find an occurrence of `matcher' from `start' to `end'.
1469 ;; Apply each highlight to this instance of `matcher', which may be
1470 ;; specific highlights or more keywords anchored to `matcher'.
1476 end))
1480 ;;; End of Syntactic regexp fontification functions.
1481 \f
1482 ;;; Syntactic fontification functions.
1484 ;; These record the parse state at a particular position, always the start of a
1485 ;; line. Used to make `font-lock-fontify-syntactically-region' faster.
1486 ;; Previously, `font-lock-cache-position' was just a buffer position. However,
1487 ;; under certain situations, this occasionally resulted in mis-fontification.
1488 ;; I think the "situations" were deletion with Lazy Lock mode's deferral. sm.
1493 "Put proper face on each string and comment between START and END.
1494 START should be at the beginning of a line."
1496 state string beg)
1499 ;;
1500 ;; Find the state at the `beginning-of-line' before `start'.
1502 ;; Use the cache for the state of `start'.
1504 ;; Find the state of `start'.
1506 ;; Use the state at the previous cache position, if any, or
1507 ;; otherwise calculate from `point-min'.
1511 font-lock-cache-state)))
1512 ;; Call the function to move outside any syntactic block.
1515 ;; Cache the state and position of `start'.
1518 ;;
1519 ;; If the region starts inside a string or comment, show the extent of it.
1525 font-lock-string-face
1526 font-lock-comment-face)))
1527 ;;
1528 ;; Find each interesting place between here and `end'.
1538 font-lock-string-face
1539 font-lock-comment-face)))))
1541 ;;; End of Syntactic fontification functions.
1542 \f
1543 ;;; Keyword regexp fontification functions.
1546 "Apply HIGHLIGHT following a match.
1547 HIGHLIGHT should be of the form MATCH-HIGHLIGHT, see `font-lock-keywords'."
1552 ;; No match but we might not signal an error.
1556 ;; Cannot override existing fontification.
1560 ;; Override existing fontification.
1563 ;; Prepend to existing fontification.
1566 ;; Append to existing fontification.
1569 ;; Keep existing fontification.
1573 "Fontify according to KEYWORDS until LIMIT.
1574 KEYWORDS should be of the form MATCH-ANCHORED, see `font-lock-keywords',
1575 LIMIT can be modified by the value of its PRE-MATCH-FORM."
1578 ;; Evaluate PRE-MATCH-FORM.
1580 ;; Set LIMIT to value of PRE-MATCH-FORM or the end of line.
1586 pre-match-value
1588 ;; this is a multiline anchored match
1592 ;; Find an occurrence of `matcher' before `limit'.
1597 ;; Apply each highlight to this instance of `matcher'.
1602 ;; Evaluate POST-MATCH-FORM.
1606 "Fontify according to `font-lock-keywords' between START and END.
1607 START should be at the beginning of a line."
1613 keyword matcher highlights)
1614 ;;
1615 ;; Fontify each item in `font-lock-keywords' from `start' to `end'.
1619 ;;
1620 ;; Find an occurrence of `matcher' from `start' to `end'.
1633 ;; this is a multiline regexp match
1637 ;; Apply each highlight to this instance of `matcher', which may be
1638 ;; specific highlights or more keywords anchored to `matcher'.
1647 ;;; End of Keyword regexp fontification functions.
1648 \f
1649 ;; Various functions.
1652 "Compile KEYWORDS into the form (t KEYWORD ...).
1653 Here KEYWORD is of the form (MATCHER HIGHLIGHT ...) as shown in the
1654 `font-lock-keywords' doc string."
1656 keywords
1665 ;; If FORM is a FACENAME then quote it. Otherwise ignore the quote.
1676 keyword)))
1679 "Evalulate KEYWORDS if a function (funcall) or variable (eval) name."
1681 keywords
1687 "Return value in ALIST for `major-mode', or ALIST if it is not an alist.
1688 Structure is ((MAJOR-MODE . VALUE) ...) where MAJOR-MODE may be t."
1691 alist))
1694 "Return LEVELth element of KEYWORDS.
1695 A LEVEL of nil is equal to a LEVEL of 0, a LEVEL of t is equal to
1696 \(1- (length KEYWORDS))."
1698 keywords)
1709 "Set fontification defaults appropriately for this mode.
1710 Sets various variables using `font-lock-defaults' (or, if nil, using
1711 `font-lock-defaults-alist') and `font-lock-maximum-decoration'."
1712 ;; Set fontification defaults iff not previously set.
1727 ;; Regexp fontification?
1730 ;; Local fontification?
1736 ;; Syntactic fontification?
1739 ;; Case fold during regexp fontification?
1742 ;; Syntax table for regexp and syntactic fontification?
1748 ;; The character to modify may be a single CHAR or a STRING.
1757 ;; Syntax function for syntactic fontification?
1761 ;; Variable alist?
1771 "Unset fontification defaults. See function `font-lock-set-defaults'."
1773 font-lock-keywords nil
1774 font-lock-keywords-only nil
1775 font-lock-keywords-case-fold-search nil
1776 font-lock-syntax-table nil
1777 font-lock-beginning-of-syntax-function nil)
1784 \f
1785 ;;; Colour etc. support.
1787 ;; Originally these variable values were face names such as `bold' etc.
1788 ;; Now we create our own faces, but we keep these variables for compatibility
1789 ;; and they give users another mechanism for changing face appearance.
1790 ;; We now allow a FACENAME in `font-lock-keywords' to be any expression that
1791 ;; returns a face. So the easiest thing is to continue using these variables,
1792 ;; rather than sometimes evaling FACENAME and sometimes not. sm.
1823 ;; Originally face attributes were specified via `font-lock-face-attributes'.
1824 ;; Users then changed the default face attributes by setting that variable.
1825 ;; However, we try and be back-compatible and respect its value if set except
1826 ;; for faces where M-x customize has been used to save changes for the face.
1832 ;; Rustle up a `defface' SPEC from a `font-lock-face-attributes' entry.
1839 face-spec)
1852 ;; But now we do it the custom way. Note that `defface' will not overwrite any
1853 ;; faces declared above via `custom-declare-face'.
1863 "Font Lock mode face used to highlight comments."
1873 "Font Lock mode face used to highlight strings."
1883 "Font Lock mode face used to highlight keywords."
1893 "Font Lock mode face used to highlight builtins."
1901 "Font Lock mode face used to highlight function names."
1913 "Font Lock mode face used to highlight variable names."
1923 "Font Lock mode face used to highlight type and classes."
1935 "Font Lock mode face used to highlight constants and labels."
1943 "Font Lock mode face used to highlight warnings."
1946 ;;; End of Colour etc. support.
1947 \f
1948 ;;; Menu support.
1950 ;; This section of code is commented out because Emacs does not have real menu
1951 ;; buttons. (We can mimic them by putting "( ) " or "(X) " at the beginning of
1952 ;; the menu entry text, but with Xt it looks both ugly and embarrassingly
1953 ;; amateur.) If/When Emacs gets real menus buttons, put in menu-bar.el after
1954 ;; the entry for "Text Properties" something like:
1955 ;;
1956 ;; (define-key menu-bar-edit-menu [font-lock]
1957 ;; (cons "Syntax Highlighting" font-lock-menu))
1958 ;;
1959 ;; and remove a single ";" from the beginning of each line in the rest of this
1960 ;; section. Probably the mechanism for telling the menu code what are menu
1961 ;; buttons and when they are on or off needs tweaking. I have assumed that the
1962 ;; mechanism is via `menu-toggle' and `menu-selected' symbol properties. sm.
1964 ;;;;###autoload
1965 ;(progn
1966 ; ;; Make the Font Lock menu.
1967 ; (defvar font-lock-menu (make-sparse-keymap "Syntax Highlighting"))
1968 ; ;; Add the menu items in reverse order.
1969 ; (define-key font-lock-menu [fontify-less]
1970 ; '("Less In Current Buffer" . font-lock-fontify-less))
1971 ; (define-key font-lock-menu [fontify-more]
1972 ; '("More In Current Buffer" . font-lock-fontify-more))
1973 ; (define-key font-lock-menu [font-lock-sep]
1974 ; '("--"))
1975 ; (define-key font-lock-menu [font-lock-mode]
1976 ; '("In Current Buffer" . font-lock-mode))
1977 ; (define-key font-lock-menu [global-font-lock-mode]
1978 ; '("In All Buffers" . global-font-lock-mode)))
1979 ;
1980 ;;;;###autoload
1981 ;(progn
1982 ; ;; We put the appropriate `menu-enable' etc. symbol property values on when
1983 ; ;; font-lock.el is loaded, so we don't need to autoload the three variables.
1984 ; (put 'global-font-lock-mode 'menu-toggle t)
1985 ; (put 'font-lock-mode 'menu-toggle t)
1986 ; (put 'font-lock-fontify-more 'menu-enable '(identity))
1987 ; (put 'font-lock-fontify-less 'menu-enable '(identity)))
1988 ;
1989 ;;; Put the appropriate symbol property values on now. See above.
1990 ;(put 'global-font-lock-mode 'menu-selected 'global-font-lock-mode)
1991 ;(put 'font-lock-mode 'menu-selected 'font-lock-mode)
1992 ;(put 'font-lock-fontify-more 'menu-enable '(nth 2 font-lock-fontify-level))
1993 ;(put 'font-lock-fontify-less 'menu-enable '(nth 1 font-lock-fontify-level))
1994 ;
1995 ;(defvar font-lock-fontify-level nil) ; For less/more fontification.
1996 ;
1997 ;(defun font-lock-fontify-level (level)
1998 ; (let ((font-lock-maximum-decoration level))
1999 ; (when font-lock-mode
2000 ; (font-lock-mode))
2001 ; (font-lock-mode)
2002 ; (when font-lock-verbose
2003 ; (message "Fontifying %s... level %d" (buffer-name) level))))
2004 ;
2005 ;(defun font-lock-fontify-less ()
2006 ; "Fontify the current buffer with less decoration.
2007 ;See `font-lock-maximum-decoration'."
2008 ; (interactive)
2009 ; ;; Check in case we get called interactively.
2010 ; (if (nth 1 font-lock-fontify-level)
2011 ; (font-lock-fontify-level (1- (car font-lock-fontify-level)))
2012 ; (error "No less decoration")))
2013 ;
2014 ;(defun font-lock-fontify-more ()
2015 ; "Fontify the current buffer with more decoration.
2016 ;See `font-lock-maximum-decoration'."
2017 ; (interactive)
2018 ; ;; Check in case we get called interactively.
2019 ; (if (nth 2 font-lock-fontify-level)
2020 ; (font-lock-fontify-level (1+ (car font-lock-fontify-level)))
2021 ; (error "No more decoration")))
2022 ;
2023 ;;; This should be called by `font-lock-set-defaults'.
2024 ;(defun font-lock-set-menu ()
2025 ; ;; Activate less/more fontification entries if there are multiple levels for
2026 ; ;; the current buffer. Sets `font-lock-fontify-level' to be of the form
2027 ; ;; (CURRENT-LEVEL IS-LOWER-LEVEL-P IS-HIGHER-LEVEL-P) for menu activation.
2028 ; (let ((keywords (or (nth 0 font-lock-defaults)
2029 ; (nth 1 (assq major-mode font-lock-defaults-alist))))
2030 ; (level (font-lock-value-in-major-mode font-lock-maximum-decoration)))
2031 ; (make-local-variable 'font-lock-fontify-level)
2032 ; (if (or (symbolp keywords) (= (length keywords) 1))
2033 ; (font-lock-unset-menu)
2034 ; (cond ((eq level t)
2035 ; (setq level (1- (length keywords))))
2036 ; ((or (null level) (zerop level))
2037 ; ;; The default level is usually, but not necessarily, level 1.
2038 ; (setq level (- (length keywords)
2039 ; (length (member (eval (car keywords))
2040 ; (mapcar 'eval (cdr keywords))))))))
2041 ; (setq font-lock-fontify-level (list level (> level 1)
2042 ; (< level (1- (length keywords))))))))
2043 ;
2044 ;;; This should be called by `font-lock-unset-defaults'.
2045 ;(defun font-lock-unset-menu ()
2046 ; ;; Deactivate less/more fontification entries.
2047 ; (setq font-lock-fontify-level nil))
2049 ;;; End of Menu support.
2050 \f
2051 ;;; Various regexp information shared by several modes.
2052 ;;; Information specific to a single mode should go in its load library.
2054 ;; Font Lock support for C, C++, Objective-C and Java modes will one day be in
2055 ;; some cc-font.el (and required by cc-mode.el). However, the below function
2056 ;; should stay in font-lock.el, since it is used by other libraries. sm.
2059 "Match, and move over, any declaration/definition item after point.
2060 Matches after point, but ignores leading whitespace and `*' characters.
2061 Does not move further than LIMIT.
2063 The expected syntax of a declaration/definition item is `word' (preceded by
2064 optional whitespace and `*' characters and proceeded by optional whitespace)
2065 optionally followed by a `('. Everything following the item (but belonging to
2066 it) is expected to by skip-able by `scan-sexps', and items are expected to be
2067 separated with a `,' and to be terminated with a `;'.
2069 Thus the regexp matches after point: word (
2070 ^^^^ ^
2071 Where the match subexpressions are: 1 2
2073 The item is delimited by (match-beginning 1) and (match-end 1).
2074 If (match-beginning 2) is non-nil, the item is followed by a `('.
2076 This function could be MATCHER in a MATCH-ANCHORED `font-lock-keywords' item."
2081 ;; Restrict to the end of line, currently guaranteed to be LIMIT.
2084 ;; Move over any item value, etc., to the next item.
2089 \f
2090 ;; Lisp.
2095 ;;
2096 ;; Definitions.
2098 ;; Function declarations.
2104 ;; Variable declarations.
2106 ;; Structure declarations.
2109 ;; Any whitespace and defined object.
2116 nil t))
2117 ;;
2118 ;; Emacs Lisp autoload cookies.
2120 ))
2127 ;;
2128 ;; Control structures. Emacs Lisp forms.
2138 "eval-when"
2145 ;;
2146 ;; Control structures. Common Lisp forms.
2160 ;;
2161 ;; Exit/Feature symbols as constants.
2166 ;;
2167 ;; Erroneous structures.
2169 ;;
2170 ;; Words inside \\[] tend to be for `substitute-command-keys'.
2172 ;;
2173 ;; Words inside `' tend to be symbol names.
2175 ;;
2176 ;; Constant values.
2178 ;;
2179 ;; ELisp and CLisp `&' keywords as types.
2181 ;;
2182 ;; CL `with-' and `do-' constructs
2184 )))
2189 \f
2190 ;; TeX.
2192 ;(defvar tex-font-lock-keywords
2193 ; ;; Regexps updated with help from Ulrik Dickow <dickow@nbi.dk>.
2194 ; '(("\\\\\\(begin\\|end\\|newcommand\\){\\([a-zA-Z0-9\\*]+\\)}"
2195 ; 2 font-lock-function-name-face)
2196 ; ("\\\\\\(cite\\|label\\|pageref\\|ref\\){\\([^} \t\n]+\\)}"
2197 ; 2 font-lock-constant-face)
2198 ; ;; It seems a bit dubious to use `bold' and `italic' faces since we might
2199 ; ;; not be able to display those fonts.
2200 ; ("{\\\\bf\\([^}]+\\)}" 1 'bold keep)
2201 ; ("{\\\\\\(em\\|it\\|sl\\)\\([^}]+\\)}" 2 'italic keep)
2202 ; ("\\\\\\([a-zA-Z@]+\\|.\\)" . font-lock-keyword-face)
2203 ; ("^[ \t\n]*\\\\def[\\\\@]\\(\\w+\\)" 1 font-lock-function-name-face keep))
2204 ; ;; Rewritten and extended for LaTeX2e by Ulrik Dickow <dickow@nbi.dk>.
2205 ; '(("\\\\\\(begin\\|end\\|newcommand\\){\\([a-zA-Z0-9\\*]+\\)}"
2206 ; 2 font-lock-function-name-face)
2207 ; ("\\\\\\(cite\\|label\\|pageref\\|ref\\){\\([^} \t\n]+\\)}"
2208 ; 2 font-lock-constant-face)
2209 ; ("^[ \t]*\\\\def\\\\\\(\\(\\w\\|@\\)+\\)" 1 font-lock-function-name-face)
2210 ; "\\\\\\([a-zA-Z@]+\\|.\\)"
2211 ; ;; It seems a bit dubious to use `bold' and `italic' faces since we might
2212 ; ;; not be able to display those fonts.
2213 ; ;; LaTeX2e: \emph{This is emphasized}.
2214 ; ("\\\\emph{\\([^}]+\\)}" 1 'italic keep)
2215 ; ;; LaTeX2e: \textbf{This is bold}, \textit{...}, \textsl{...}
2216 ; ("\\\\text\\(\\(bf\\)\\|it\\|sl\\){\\([^}]+\\)}"
2217 ; 3 (if (match-beginning 2) 'bold 'italic) keep)
2218 ; ;; Old-style bf/em/it/sl. Stop at `\\' and un-escaped `&', for tables.
2219 ; ("\\\\\\(\\(bf\\)\\|em\\|it\\|sl\\)\\>\\(\\([^}&\\]\\|\\\\[^\\]\\)+\\)"
2220 ; 3 (if (match-beginning 2) 'bold 'italic) keep))
2222 ;; Rewritten with the help of Alexandra Bac <abac@welcome.disi.unige.it>.
2232 t))
2236 t))
2241 t))
2242 ;; Miscellany.
2247 ;; Heading args.
2250 ;; Variable args.
2252 ;; Include args.
2254 ;; Definitions. I think.
2257 )))
2264 ;; Names of commands whose arg should be fontified with fonts.
2269 ;;
2270 ;; Names of commands whose arg should be fontified as a citation.
2275 t))
2276 ;;
2277 ;; Names of commands that should be fontified.
2283 t))
2285 ;;
2286 ;; Miscellany.
2291 ;;
2292 ;; Citation args.
2294 ;;
2295 ;; Command names, special and general.
2298 ;;
2299 ;; Font environments. It seems a bit dubious to use `bold' etc. faces
2300 ;; since we might not be able to display those fonts.
2304 ;;
2305 ;; Old-style bf/em/it/sl. Stop at `\\' and un-escaped `&', for tables.
2309 ))))
2314 \f
2315 ;;; User choices.
2317 ;; These provide a means to fontify types not defined by the language. Those
2318 ;; types might be the user's own or they might be generally accepted and used.
2319 ;; Generally accepted types are used to provide default variable values.
2322 "Widget `:type' for members of the custom group `font-lock-extra-types'.
2323 Members should `:load' the package `font-lock' to use this widget."
2328 "*List of extra types to fontify in C mode.
2329 Each list item should be a regexp not containing word-delimiters.
2331 ending in _t are treated as type names.
2333 The value of this variable is used when Font Lock mode is turned on."
2347 "type_info"
2350 "*List of extra types to fontify in C++ mode.
2351 Each list item should be a regexp not containing word-delimiters.
2353 name.
2355 The value of this variable is used when Font Lock mode is turned on."
2360 "*List of extra types to fontify in Objective-C mode.
2361 Each list item should be a regexp not containing word-delimiters.
2363 Class, BOOL, IMP and SEL are treated as type names.
2365 The value of this variable is used when Font Lock mode is turned on."
2371 "*List of extra types to fontify in Java mode.
2372 Each list item should be a regexp not containing word-delimiters.
2374 words (and words conforming to the Java id spec) are treated as type names.
2376 The value of this variable is used when Font Lock mode is turned on."
2379 \f
2380 ;;; C.
2382 ;; [Murmur murmur murmur] Maestro, drum-roll please... [Murmur murmur murmur.]
2383 ;; Ahem. [Murmur murmur murmur] Lay-dees an Gennel-men. [Murmur murmur shhh!]
2384 ;; I am most proud and humbly honoured today [murmur murmur cough] to present
2385 ;; to you good people, the winner of the Second Millennium Award for The Most
2386 ;; Hairy Language Syntax. [Ahhh!] All rise please. [Shuffle shuffle
2387 ;; shuffle.] And a round of applause please. For... The C Language! [Roar.]
2388 ;;
2389 ;; Thank you... You are too kind... It is with a feeling of great privilege
2390 ;; and indeed emotion [sob] that I accept this award. It has been a long hard
2391 ;; road. But we know our destiny. And our future. For we must not rest.
2392 ;; There are more tokens to overload, more shoehorn, more methodologies. But
2393 ;; more is a plus! [Ha ha ha.] And more means plus! [Ho ho ho.] The future
2394 ;; is C++! [Ohhh!] The Third Millennium Award... Will be ours! [Roar.]
2400 "Medium level highlighting for C mode.
2404 "Gaudy level highlighting for C mode.
2411 ;; Type related, but we don't do anything special.
2414 ;; Dan Nicolaescu <done@gnu.org> says this is new.
2428 c-font-lock-extra-types)
2441 ;;
2442 ;; These are all anchored at the beginning of line for speed.
2443 ;; Note that `c++-font-lock-keywords-1' depends on `c-font-lock-keywords-1'.
2444 ;;
2445 ;; Fontify function name definitions (GNU style; without type on line).
2447 ;;
2448 ;; Fontify error directives.
2450 ;;
2451 ;; Fontify filenames in #include <...> preprocessor directives as strings.
2454 ;;
2455 ;; Fontify function macro names.
2457 ;;
2458 ;; Fontify symbol names in #elif or #if ... defined preprocessor directives.
2462 ;;
2463 ;; Fontify otherwise as symbol names, and the preprocessor directive names.
2474 ;;
2475 ;; Simple regexps for speed.
2476 ;;
2477 ;; Fontify all type names.
2480 ;;
2481 ;; Fontify all builtin keywords (except case, default and goto; see below).
2483 ;;
2484 ;; Fontify case/goto keywords and targets, and case default/goto tags.
2488 ;; Return limit of search.
2490 nil
2492 ;; Anders Lindgren <andersl@andersl.com> points out that it is quicker to
2493 ;; use MATCH-ANCHORED to effectively anchor the regexp on the left.
2494 ;; This must come after the one for keywords and targets.
2498 )))
2502 ;;
2503 ;; More complicated regexps for more complete highlighting for types.
2504 ;; We still have to fontify type specifiers individually, as C is so hairy.
2506 ;;
2507 ;; Fontify all storage types, plus their items.
2511 ;; Fontify each declaration item.
2513 ;; Start with point after all type specifiers.
2518 ;; Finish with point after first type specifier.
2520 ;; Fontify as a variable or function name.
2522 font-lock-function-name-face
2523 font-lock-variable-name-face)))))
2524 ;;
2525 ;; Fontify all storage specs and types, plus their items.
2532 nil nil
2533 ;; Fontify as a variable or function name.
2535 font-lock-function-name-face
2537 ;;
2538 ;; Fontify structures, or typedef names, plus their items.
2543 ;;
2544 ;; Fontify anything at beginning of line as a declaration or definition.
2550 font-lock-function-name-face
2551 font-lock-variable-name-face))))
2552 )))
2553 )
2556 "Default expressions to highlight in C mode.
2558 \f
2559 ;;; C++.
2565 "Medium level highlighting for C++ mode.
2569 "Gaudy level highlighting for C++ mode.
2573 ;; Regexp matches after point: word<word>::word (
2574 ;; ^^^^ ^^^^ ^^^^ ^
2575 ;; Where the match subexpressions are: 1 3 5 6
2576 ;;
2577 ;; Item is delimited by (match-beginning 1) and (match-end 1).
2578 ;; If (match-beginning 3) is non-nil, that part of the item incloses a `<>'.
2579 ;; If (match-beginning 5) is non-nil, that part of the item follows a `::'.
2580 ;; If (match-beginning 6) is non-nil, the item is followed by a `('.
2583 ;; Skip any leading whitespace.
2585 ;; This is `c++-type-spec' from below. (Hint hint!)
2589 ;; Match any trailing parenthesis.
2594 ;; Restrict to the end of line, currently guaranteed to be LIMIT.
2597 ;; Move over any item value, etc., to the next item.
2604 ;; Match C++ constructors and destructors inside class declarations.
2610 ;; Don't match function pointer declarations, e.g.:
2611 ;; Foo (*fptr)();
2619 res))
2626 "typeid"
2627 ;; Branko Cibej <branko.cibej@hermes.si> says this is new.
2628 "export"
2629 ;; Mark Mitchell <mmitchell@usa.net> says these are new.
2631 ;; Alain Picard <ap@abelard.apana.org.au> suggests treating these
2632 ;; as keywords not types.
2639 ;; Taken from Stroustrup, minus keywords otherwise fontified.
2648 ;; Eric Hopper <hopper@omnifarious.mn.org> says these are new.
2663 ;;
2664 ;; A brave attempt to match templates following a type and/or match
2665 ;; class membership. See and sync the above function
2666 ;; `font-lock-match-c++-style-declaration-item-and-skip-to-next'.
2670 ;; If the string is a type, it may be followed by the cruft above.
2673 ;;
2674 ;; Parenthesis depth of user-defined types not forgetting their cruft.
2677 )
2680 ;;
2681 ;; The list `c-font-lock-keywords-1' less that for function names.
2684 ;;
2685 ;; Fontify function name definitions, possibly incorporating class names.
2688 font-lock-type-face
2689 font-lock-function-name-face))
2692 )))
2697 ;;
2698 ;; The list `c-font-lock-keywords-2' for C++ plus operator overloading.
2702 ;;
2703 ;; Fontify operator overloading.
2707 ;;
2708 ;; Fontify case/goto keywords and targets, and case default/goto tags.
2712 ;; Return limit of search.
2719 nil
2721 font-lock-type-face
2723 ;; This must come after the one for keywords and targets.
2727 ;;
2728 ;; Fontify other builtin keywords.
2730 ;;
2731 ;; Eric Hopper <hopper@omnifarious.mn.org> says `true' and `false' are new.
2733 )))
2737 ;;
2738 ;; More complicated regexps for more complete highlighting for types.
2740 ;;
2741 ;; Fontify all storage classes and type specifiers, plus their items.
2745 ;; The name of any template type.
2747 ;; Fontify each declaration item.
2749 ;; Start with point after all type specifiers.
2753 ;; Finish with point after first type specifier.
2755 ;; Fontify as a variable or function name.
2757 font-lock-type-face)
2759 font-lock-function-name-face)
2761 font-lock-variable-name-face)))
2764 font-lock-function-name-face
2766 ;;
2767 ;; Fontify all storage specs and types, plus their items.
2771 ;; The name of any template type.
2773 ;; The name of any type.
2776 ;; Fontify each declaration item.
2778 ;; Start with point after all type specifiers.
2779 nil
2780 ;; Finish with point after first type specifier.
2781 nil
2782 ;; Fontify as a variable or function name.
2784 font-lock-type-face)
2786 font-lock-function-name-face)
2788 font-lock-variable-name-face)))
2791 font-lock-function-name-face
2793 ))
2794 ;;
2795 ;; Fontify structures, or typedef names, plus their items.
2800 ;;
2801 ;; Fontify anything at beginning of line as a declaration or definition.
2807 font-lock-type-face)
2812 font-lock-function-name-face
2814 ;;
2815 ;; Fontify constructors and destructors inside class declarations.
2818 )))
2819 )
2822 "Default expressions to highlight in C++ mode.
2824 \f
2825 ;;; Objective-C.
2831 "Medium level highlighting for Objective-C mode.
2835 "Gaudy level highlighting for Objective-C mode.
2838 ;; Regexps written with help from Stephen Peters <speters@us.oracle.com> and
2839 ;; Jacques Duthen Prestataire <duthen@cegelec-red.fr>.
2861 objc-font-lock-extra-types)
2865 )
2868 ;;
2869 ;; The list `c-font-lock-keywords-1' less that for function names.
2872 ;;
2873 ;; Fontify compiler directives.
2878 ;;
2879 ;; Fontify method names and arguments. Oh Lordy!
2880 ;; First, on the same line as the function declaration.
2885 nil nil
2888 ;; Second, on lines following the function declaration.
2893 )))
2898 ;;
2899 ;; Simple regexps for speed.
2900 ;;
2901 ;; Fontify all type specifiers.
2905 ;;
2906 ;; Fontify all builtin keywords (except case, default and goto; see below).
2908 ;;
2909 ;; Fontify case/goto keywords and targets, and case default/goto tags.
2912 ;; Fontify tags iff sole statement on line, otherwise we detect selectors.
2913 ;; This must come after the one for keywords and targets.
2917 ;;
2918 ;; Fontify null object pointers.
2920 )))
2924 ;;
2925 ;; More complicated regexps for more complete highlighting for types.
2926 ;; We still have to fontify type specifiers individually, as C is so hairy.
2928 ;;
2929 ;; Fontify all storage classes and type specifiers, plus their items.
2933 ;; Fontify each declaration item.
2935 ;; Start with point after all type specifiers.
2940 ;; Finish with point after first type specifier.
2942 ;; Fontify as a variable or function name.
2944 font-lock-function-name-face
2945 font-lock-variable-name-face)))))
2946 ;;
2947 ;; Fontify all storage specs and types, plus their items.
2951 ;; The name of any type.
2953 ;; Fontify each declaration item.
2955 nil nil
2956 ;; Fontify as a variable or function name.
2958 font-lock-function-name-face
2959 font-lock-variable-name-face)))
2960 ))
2961 ;;
2962 ;; Fontify structures, or typedef names, plus their items.
2967 ;;
2968 ;; Fontify anything at beginning of line as a declaration or definition.
2974 font-lock-function-name-face
2975 font-lock-variable-name-face))))
2976 )))
2977 )
2980 "Default expressions to highlight in Objective-C mode.
2982 \f
2983 ;;; Java.
2989 "Medium level highlighting for Java mode.
2993 "Gaudy level highlighting for Java mode.
2996 ;; Regexps written with help from Fred White <fwhite@bbn.com>,
2997 ;; Anders Lindgren <andersl@andersl.com> and Carl Manning <caroma@ai.mit.edu>.
3002 ;; Anders Lindgren <andersl@andersl.com> says these have gone.
3003 ;; "cast" "byvalue" "future" "generic" "operator" "var"
3004 ;; "inner" "outer" "rest"
3007 ;;
3008 ;; Classes immediately followed by an object name.
3015 java-font-lock-extra-types)
3018 ;;
3019 ;; These are eventually followed by an object name.
3024 ;; Anders Lindgren <andersl@andersl.com> says this has gone.
3025 ;; "threadsafe"
3027 ;; Carl Manning <caroma@ai.mit.edu> says this is new.
3029 )
3032 ;;
3033 ;; Fontify class names.
3036 ;;
3037 ;; Fontify package names in import directives.
3043 ))
3048 ;;
3049 ;; Fontify class names.
3053 ;;
3054 ;; Fontify all builtin keywords (except below).
3056 ;;
3057 ;; Fontify keywords and targets, and case default/goto tags.
3060 ;; This must come after the one for keywords and targets.
3064 ;;
3065 ;; Fontify all constants.
3067 ;;
3068 ;; Javadoc tags within comments.
3082 )))
3086 ;;
3087 ;; More complicated regexps for more complete highlighting for types.
3088 ;; We still have to fontify type specifiers individually, as Java is hairy.
3090 ;;
3091 ;; Fontify random types immediately followed by an item or items.
3096 ;; Fontify each declaration item.
3098 ;; Start and finish with point after the type specifier.
3103 ;; Fontify as a variable or function name.
3105 font-lock-function-name-face
3106 font-lock-variable-name-face)))))
3107 ;;
3108 ;; Fontify those that are eventually followed by an item or items.
3113 ;; Fontify each declaration item.
3115 ;; Start with point after all type specifiers.
3117 ;; Finish with point after first type specifier.
3119 ;; Fontify as a variable or function name.
3121 font-lock-function-name-face
3122 font-lock-variable-name-face))))
3123 )))
3124 )
3127 "Default expressions to highlight in Java mode.
3129 \f
3130 ;; Install ourselves:
3132 ;; Useful for the popup-menu for mouse-3 on the modeline.
3136 ;; Provide ourselves:
3141 ;;; font-lock.el ends here