| blob | ad69cdd960c27ec8884732e853100a97c94d9c80 |
1 ;;; font-lock.el --- Electric font lock mode
3 ;; Copyright (C) 1992, 93, 94, 95, 96, 97, 98, 1999, 2000, 2001, 02, 2003, 2004
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 ;; (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:
212 ;; Define core `font-lock' group.
214 "Font Lock mode text highlighting package."
220 "Faces for highlighting text."
225 "Extra mode-specific type names for highlighting declarations."
228 ;; Define support mode groups here to impose `font-lock' group order.
230 "Font Lock support mode to cache fontification."
236 "Font Lock support mode to fontify lazily."
240 \f
241 ;; User variables.
244 "*Maximum size of a buffer for buffer fontification.
245 Only buffers less than this can be fontified when Font Lock mode is turned on.
246 If nil, means size is irrelevant.
247 If a list, each element should be a cons pair of the form (MAJOR-MODE . SIZE),
248 where MAJOR-MODE is a symbol or t (meaning the default). For example:
249 ((c-mode . 256000) (c++-mode . 256000) (rmail-mode . 1048576))
250 means that the maximum size is 250K for buffers in C or C++ modes, one megabyte
251 for buffers in Rmail mode, and size is irrelevant otherwise."
266 "*Maximum decoration level for fontification.
267 If nil, use the default decoration (typically the minimum available).
268 If t, use the maximum decoration available.
269 If a number, use that level of decoration (or if not available the maximum).
270 If a list, each element should be a cons pair of the form (MAJOR-MODE . LEVEL),
271 where MAJOR-MODE is a symbol or t (meaning the default). For example:
272 ((c-mode . t) (c++-mode . 2) (t . 1))
273 means use the maximum decoration available for buffers in C mode, level 2
274 decoration for buffers in C++ mode, and level 1 decoration otherwise."
291 "*If non-nil, means show status messages for buffer fontification.
292 If a number, only buffers greater than this size have fontification messages."
297 \f
299 ;; Originally these variable values were face names such as `bold' etc.
300 ;; Now we create our own faces, but we keep these variables for compatibility
301 ;; and they give users another mechanism for changing face appearance.
302 ;; We now allow a FACENAME in `font-lock-keywords' to be any expression that
303 ;; returns a face. So the easiest thing is to continue using these variables,
304 ;; rather than sometimes evaling FACENAME and sometimes not. sm.
341 ;; Fontification variables:
344 "A list of the keywords to highlight.
345 Each element should have one of these forms:
347 MATCHER
348 (MATCHER . MATCH)
349 (MATCHER . FACENAME)
350 (MATCHER . HIGHLIGHT)
351 (MATCHER HIGHLIGHT ...)
352 (eval . FORM)
354 where MATCHER can be either the regexp to search for, or the function name to
355 call to make the search (called with one argument, the limit of the search) and
356 return non-nil if it succeeds (and set `match-data' appropriately).
357 MATCHER regexps can be generated via the function `regexp-opt'.
359 FORM is an expression, whose value should be a keyword element, evaluated when
360 the keyword is (first) used in a buffer. This feature can be used to provide a
361 keyword that can only be generated when Font Lock mode is actually turned on.
363 HIGHLIGHT should be either MATCH-HIGHLIGHT or MATCH-ANCHORED.
366 typically only MATCH-HIGHLIGHT is required.
367 However, if an item or (typically) items are to be highlighted following the
368 instance of another item (the anchor), for example each instance of the
371 MATCH-HIGHLIGHT should be of the form:
373 (MATCH FACENAME OVERRIDE LAXMATCH)
375 MATCH is the subexpression of MATCHER to be highlighted. FACENAME is an
376 expression whose value is the face name to use. Face default attributes
378 evaluate to a property list of the form (face VAL1 PROP2 VAL2 PROP3 VAL3 ...)
379 in which case all the listed text-properties will be set rather than
380 just `face'. In such a case, you will most likely want to put those
381 properties in `font-lock-extra-managed-props' or to override
382 `font-lock-unfontify-region-function'.
384 OVERRIDE and LAXMATCH are flags. If OVERRIDE is t, existing fontification can
385 be overwritten. If `keep', only parts not already fontified are highlighted.
386 If `prepend' or `append', existing fontification is merged with the new, in
387 which the new or existing fontification, respectively, takes precedence.
388 If LAXMATCH is non-nil, no error is signaled if there is no MATCH in MATCHER.
390 For example, an element of the form highlights (if not already highlighted):
393 variable `font-lock-keyword-face'.
395 the value of `font-lock-keyword-face'.
399 of `foo-bar-face', even if already highlighted.
400 (fubar-match 1 fubar-face)
401 the first subexpression within all occurrences of
402 whatever the function `fubar-match' finds and matches
403 in the value of `fubar-face'.
405 MATCH-ANCHORED should be of the form:
407 (MATCHER PRE-MATCH-FORM POST-MATCH-FORM MATCH-HIGHLIGHT ...)
409 where MATCHER is a regexp to search for or the function name to call to make
410 the search, as for MATCH-HIGHLIGHT above, but with one exception; see below.
411 PRE-MATCH-FORM and POST-MATCH-FORM are evaluated before the first, and after
412 the last, instance MATCH-ANCHORED's MATCHER is used. Therefore they can be
413 used to initialise before, and cleanup after, MATCHER is used. Typically,
414 PRE-MATCH-FORM is used to move to some position relative to the original
415 MATCHER, before starting with MATCH-ANCHORED's MATCHER. POST-MATCH-FORM might
416 be used to move, before resuming with MATCH-ANCHORED's parent's MATCHER.
418 For example, an element of the form highlights (if not already highlighted):
429 The above-mentioned exception is as follows. The limit of the MATCHER search
430 defaults to the end of the line after PRE-MATCH-FORM is evaluated.
431 However, if PRE-MATCH-FORM returns a position greater than the position after
432 PRE-MATCH-FORM is evaluated, that position is used as the limit of the search.
433 It is generally a bad idea to return a position greater than the end of the
434 line, i.e., cause the MATCHER search to span lines.
436 These regular expressions can match text which spans lines, although
437 it is better to avoid it if possible since updating them while editing
438 text is slower, and it is not guaranteed to be always correct when using
439 support modes like jit-lock or lazy-lock.
441 This variable is set by major modes via the variable `font-lock-defaults'.
442 Be careful when composing regexps for this list; a poorly written pattern can
446 "*Alist of `font-lock-keywords' local to a `major-mode'.
447 This is normally set via `font-lock-add-keywords' and
451 "*Alist of `font-lock-keywords' removed from `major-mode'.
452 This is normally set via `font-lock-add-keywords' and
456 "*Non-nil means Font Lock should not fontify comments or strings.
460 "*Non-nil means the patterns in `font-lock-keywords' are case-insensitive.
465 "Point up to which `font-lock-syntactic-keywords' has been applied.
466 If nil, this is ignored, in which case the syntactic fontification may
473 "Function to determine which face to use when fontifying syntactically.
474 The function is called with a single parameter (the state as returned by
475 `parse-partial-sexp' at the beginning of the region to highlight) and
479 "A list of the syntactic keywords to highlight.
480 Can be the list or the name of a function or variable whose value is the list.
481 See `font-lock-keywords' for a description of the form of this list;
482 the differences are listed below. MATCH-HIGHLIGHT should be of the form:
484 (MATCH SYNTAX OVERRIDE LAXMATCH)
486 where SYNTAX can be a string (as taken by `modify-syntax-entry'), a syntax
487 table, a cons cell (as returned by `string-to-syntax') or an expression whose
488 value is such a form. OVERRIDE cannot be `prepend' or `append'.
490 For example, an element of the form highlights syntactically:
494 a hash character when following a dollar character, with a SYNTAX of
496 specify hash characters to have comment start syntax, the element will only
497 highlight hash characters that do not follow dollar characters as comments
498 syntactically.
504 both single quotes which surround a single character, with a SYNTAX of
506 does not specify single quotes to have quote syntax, the element will only
507 highlight single quotes of the form 'c' as strings syntactically.
508 Other forms, such as foo'bar or 'fubar', will not be highlighted as strings.
513 "Non-nil means use this syntax table for fontifying.
514 If this is nil, the major mode's syntax table is used.
518 "*Non-nil means use this function to move back outside all constructs.
519 When called with no args it should move point backward to a place which
520 is not in a string or comment and not within any bracket-pairs (or else,
521 a place such that any bracket-pairs outside it can be ignored for Emacs
522 syntax analysis and fontification).
524 If this is nil, the beginning of the buffer is used, which is
525 always correct but tends to be slow.
526 This is normally set via `font-lock-defaults'.
527 This variable is semi-obsolete; we recommend setting
531 "*Non-nil means use this function to mark a block of text.
532 When called with no args it should leave point at the beginning of any
533 enclosing textual block and mark at the end.
537 "Function to use for fontifying the buffer.
541 "Function to use for unfontifying the buffer.
542 This is used when turning off Font Lock mode.
546 "Function to use for fontifying a region.
547 It should take two args, the beginning and end of the region, and an optional
548 third arg VERBOSE. If non-nil, the function should print status messages.
552 "Function to use for unfontifying a region.
553 It should take two args, the beginning and end of the region.
557 "List of Font Lock mode related modes that should not be turned on.
558 Currently, valid mode names are `fast-lock-mode', `jit-lock-mode' and
562 "Whether font-lock should cater to multiline keywords.
563 If nil, don't try to handle multiline patterns.
564 If t, always handle multiline patterns.
565 If `undecided', don't try to handle multiline patterns until you see one.
569 \f
570 ;; Font Lock mode.
573 ;;
574 ;; We don't do this at the top-level as we only use non-autoloaded macros.
576 ;;
577 ;; Borrowed from lazy-lock.el.
578 ;; We use this to preserve or protect things when modifying text properties.
580 "Bind variables according to VARLIST and eval BODY restoring buffer state."
588 deactivate-mark
589 buffer-file-name
590 buffer-file-truename))
597 ;;
598 ;; Shut up the byte compiler.
601 ;;;###autoload
603 ;; Turn on Font Lock mode.
608 ;; Fontify the buffer if we have to.
611 nil)
617 ;; Turn off Font Lock mode.
623 ;;;###autoload
625 "Add highlighting KEYWORDS for MODE.
626 MODE should be a symbol, the major mode command name, such as `c-mode'
627 or nil. If nil, highlighting keywords are added for the current buffer.
628 KEYWORDS should be a list; see the variable `font-lock-keywords'.
629 By default they are added at the beginning of the current highlighting list.
630 If optional argument APPEND is `set', they are used to replace the current
631 highlighting list. If APPEND is any other non-nil value, they are added at the
632 end of the current highlighting list.
634 For example:
636 (font-lock-add-keywords 'c-mode
640 adds two fontification patterns for C mode, to fontify `FIXME:' words, even in
641 comments, and to fontify `and', `or' and `not' words as keywords.
643 When used from an elisp package (such as a minor mode), it is recommended
644 to use nil for MODE (and place the call in a loop or on a hook) to avoid
645 subtle problems due to details of the implementation.
647 Note that some modes have specialized support for additional patterns, e.g.,
648 see the variables `c-font-lock-extra-types', `c++-font-lock-extra-types',
649 `objc-font-lock-extra-types' and `java-font-lock-extra-types'."
651 ;; If MODE is non-nil, add the KEYWORDS and APPEND spec to
652 ;; `font-lock-keywords-alist' so `font-lock-set-defaults' uses them.
659 ;; Make sure that `font-lock-removed-keywords-alist' does not
660 ;; contain the new keywords.
663 ;; Otherwise set or add the keywords now.
670 font-lock-keywords)))
676 ;; Update `font-lock-removed-keywords-alist' when adding new
677 ;; KEYWORDS to MODE.
678 ;;
679 ;; When font-lock is enabled first all keywords in the list
680 ;; `font-lock-keywords-alist' are added, then all keywords in the
681 ;; list `font-lock-removed-keywords-alist' are removed. If a
682 ;; keyword was once added, removed, and then added again it must be
683 ;; removed from the removed-keywords list. Otherwise the second add
684 ;; will not take effect.
688 ;; A new set of keywords is defined. Forget all about
689 ;; our old keywords that should be removed.
692 ;; Delete all previously removed keywords.
695 ;; Delete the mode cell if empty.
700 ;; Written by Anders Lindgren <andersl@andersl.com>.
701 ;;
702 ;; Case study:
703 ;; (I) The keywords are removed from a major mode.
704 ;; In this case the keyword could be local (i.e. added earlier by
705 ;; `font-lock-add-keywords'), global, or both.
706 ;;
707 ;; (a) In the local case we remove the keywords from the variable
708 ;; `font-lock-keywords-alist'.
709 ;;
710 ;; (b) The actual global keywords are not known at this time.
711 ;; All keywords are added to `font-lock-removed-keywords-alist',
712 ;; when font-lock is enabled those keywords are removed.
713 ;;
714 ;; Note that added keywords are taken out of the list of removed
715 ;; keywords. This ensure correct operation when the same keyword
716 ;; is added and removed several times.
717 ;;
718 ;; (II) The keywords are removed from the current buffer.
719 ;;;###autoload
721 "Remove highlighting KEYWORDS for MODE.
723 MODE should be a symbol, the major mode command name, such as `c-mode'
724 or nil. If nil, highlighting keywords are removed for the current buffer.
726 When used from an elisp package (such as a minor mode), it is recommended
727 to use nil for MODE (and place the call in a loop or on a hook) to avoid
728 subtle problems due to details of the implementation."
730 ;; Remove one keyword at the time.
733 ;; If MODE is non-nil, remove the KEYWORD from
734 ;; `font-lock-keywords-alist'.
737 ;; `keywords-list-append-pair' is a cons with a list of
738 ;; keywords in the car top-cell and the original append
739 ;; argument in the cdr top-cell.
742 ;; Remove keyword list/append pair when the keyword list
743 ;; is empty and append doesn't specify `set'. (If it
744 ;; should be deleted then previously deleted keywords
745 ;; would appear again.)
752 ;; Final cleanup, remove major mode cell if last keyword
753 ;; was deleted.
757 ;; Remember the keyword in case it is not local.
763 font-lock-removed-keywords-alist))))))
765 ;; Otherwise remove it immediately.
771 ;; The keywords might be compiled.
773 font-lock-keywords)))))))
774 \f
775 ;;; Font Lock Support mode.
777 ;; This is the code used to interface font-lock.el with any of its add-on
778 ;; packages, and provide the user interface. Packages that have their own
779 ;; local buffer fontification functions (see below) may have to call
780 ;; `font-lock-after-fontify-buffer' and/or `font-lock-after-unfontify-buffer'
781 ;; themselves.
784 "*Support mode for Font Lock mode.
785 Support modes speed up Font Lock mode by being choosy about when fontification
786 occurs. Known support modes are Fast Lock mode (symbol `fast-lock-mode'),
787 Lazy Lock mode (symbol `lazy-lock-mode'), and Just-in-time Lock mode (symbol
788 `jit-lock-mode'. See those modes for more info.
789 If nil, means support for Font Lock mode is never performed.
790 If a symbol, use that support mode.
791 If a list, each element should be of the form (MAJOR-MODE . SUPPORT-MODE),
792 where MAJOR-MODE is a symbol or t (meaning the default). For example:
793 ((c-mode . fast-lock-mode) (c++-mode . fast-lock-mode) (t . lazy-lock-mode))
794 means that Fast Lock mode is used to support Font Lock mode for buffers in C or
795 C++ modes, and Lazy Lock mode is used to support Font Lock mode otherwise.
797 The value of this variable is used when Font Lock mode is turned on."
813 ))
828 ;; Prepare for jit-lock
833 ;; Don't fontify eagerly (and don't abort is the buffer is large).
835 ;; Use jit-lock.
844 ;; Reset local vars to the non-jit-lock case.
852 ;; Useless now that jit-lock intercepts font-lock-fontify-buffer. -sm
853 ;; (jit-lock-mode
854 ;; (jit-lock-after-fontify-buffer))
861 ;; Useless as well. It's only called when:
862 ;; - turning off font-lock: it does not matter if we leave spurious
863 ;; `fontified' text props around since jit-lock-mode is also off.
864 ;; - font-lock-default-fontify-buffer fails: this is not run
865 ;; any more anyway. -sm
866 ;;
867 ;; (jit-lock-mode
868 ;; (jit-lock-after-unfontify-buffer))
872 ;;; End of Font Lock Support mode.
873 \f
874 ;;; Fontification functions.
876 ;; Rather than the function, e.g., `font-lock-fontify-region' containing the
877 ;; code to fontify a region, the function runs the function whose name is the
878 ;; value of the variable, e.g., `font-lock-fontify-region-function'. Normally,
879 ;; the value of this variable is, e.g., `font-lock-default-fontify-region'
880 ;; which does contain the code to fontify a region. However, the value of the
881 ;; variable could be anything and thus, e.g., `font-lock-fontify-region' could
882 ;; do anything. The indirection of the fontification functions gives major
883 ;; modes the capability of modifying the way font-lock.el fontifies. Major
884 ;; modes can modify the values of, e.g., `font-lock-fontify-region-function',
885 ;; via the variable `font-lock-defaults'.
886 ;;
887 ;; For example, Rmail mode sets the variable `font-lock-defaults' so that
888 ;; font-lock.el uses its own function for buffer fontification. This function
889 ;; makes fontification be on a message-by-message basis and so visiting an
890 ;; RMAIL file is much faster. A clever implementation of the function might
891 ;; fontify the headers differently than the message body. (It should, and
892 ;; correspondingly for Mail mode, but I can't be bothered to do the work. Can
893 ;; you?) This hints at a more interesting use...
894 ;;
895 ;; Languages that contain text normally contained in different major modes
896 ;; could define their own fontification functions that treat text differently
897 ;; depending on its context. For example, Perl mode could arrange that here
898 ;; docs are fontified differently than Perl code. Or Yacc mode could fontify
899 ;; rules one way and C code another. Neat!
900 ;;
901 ;; A further reason to use the fontification indirection feature is when the
902 ;; default syntactual fontification, or the default fontification in general,
903 ;; is not flexible enough for a particular major mode. For example, perhaps
904 ;; comments are just too hairy for `font-lock-fontify-syntactically-region' to
905 ;; cope with. You need to write your own version of that function, e.g.,
906 ;; `hairy-fontify-syntactically-region', and make your own version of
907 ;; `hairy-fontify-region' call that function before calling
908 ;; `font-lock-fontify-keywords-region' for the normal regexp fontification
909 ;; pass. And Hairy mode would set `font-lock-defaults' so that font-lock.el
910 ;; would call your region fontification function instead of its own. For
911 ;; example, TeX modes could fontify {\foo ...} and \bar{...} etc. multi-line
912 ;; directives correctly and cleanly. (It is the same problem as fontifying
913 ;; multi-line strings and comments; regexps are not appropriate for the job.)
915 ;;;###autoload
917 "Fontify the current buffer the way the function `font-lock-mode' would."
934 font-lock-verbose)))
938 ;; Make sure we have the right `font-lock-keywords' etc.
941 ;; Make sure we fontify etc. in the whole buffer.
950 ;; We don't restore the old fontification, so it's best to unfontify.
954 ;; Make sure we unfontify etc. in the whole buffer.
962 "If non-nil, font-lock will work on the non-widened buffer.
963 Useful for things like RMAIL and Info where the whole buffer is not
973 ;; Use the fontification syntax table, if any.
976 ;; check to see if we should expand the beg/end area for
977 ;; proper multiline matches
981 ;; We are just after or in a multiline match.
993 ;; Now do the fontification.
1000 ;; Clean up.
1003 ;; The following must be rethought, since keywords can override fontification.
1004 ; ;; Now scan for keywords, but not if we are inside a comment now.
1005 ; (or (and (not font-lock-keywords-only)
1006 ; (let ((state (parse-partial-sexp beg end nil nil
1007 ; font-lock-cache-state)))
1008 ; (or (nth 4 state) (nth 7 state))))
1009 ; (font-lock-fontify-keywords-region beg end))
1012 "Additional text properties managed by font-lock.
1013 This is used by `font-lock-default-unfontify-region' to decide
1020 font-lock-extra-managed-props
1025 ;; Called when any modification is made to buffer text.
1031 ;; Rescan between start of lines enclosing the region.
1037 "Fontify some lines the way `font-lock-fontify-buffer' would.
1038 The lines could be a function or paragraph, or a specified number of lines.
1039 If ARG is given, fontify that many lines before and after point, or 16 lines if
1040 no ARG is given and `font-lock-mark-block-function' is nil.
1041 If `font-lock-mark-block-function' non-nil and no ARG is given, it is used to
1042 delimit the region to fontify."
1045 deactivate-mark)
1046 ;; Make sure we have the right `font-lock-keywords' etc.
1063 ;;; End of Fontification functions.
1064 \f
1065 ;;; Additional text property functions.
1067 ;; The following text property functions should be builtins. This means they
1068 ;; should be written in C and put with all the other text property functions.
1069 ;; In the meantime, those that are used by font-lock.el are defined in Lisp
1070 ;; below and given a `font-lock-' prefix. Those that are not used are defined
1071 ;; in Lisp below and commented out. sm.
1074 "Prepend to one property of the text from START to END.
1075 Arguments PROP and VALUE specify the property and value to prepend to the value
1076 already in place. The resulting property values are always lists.
1077 Optional argument OBJECT is the string or buffer containing the text."
1084 object)
1088 "Append to one property of the text from START to END.
1089 Arguments PROP and VALUE specify the property and value to append to the value
1090 already in place. The resulting property values are always lists.
1091 Optional argument OBJECT is the string or buffer containing the text."
1098 object)
1102 "Fill in one property of the text from START to END.
1103 Arguments PROP and VALUE specify the property and value to put where none are
1104 already in place. Therefore existing property values are not overwritten.
1105 Optional argument OBJECT is the string or buffer containing the text."
1112 ;; For completeness: this is to `remove-text-properties' as `put-text-property'
1113 ;; is to `add-text-properties', etc.
1114 ;(defun remove-text-property (start end property &optional object)
1115 ; "Remove a property from text from START to END.
1116 ;Argument PROPERTY is the property to remove.
1117 ;Optional argument OBJECT is the string or buffer containing the text.
1118 ;Return t if the property was actually removed, nil otherwise."
1119 ; (remove-text-properties start end (list property) object))
1121 ;; For consistency: maybe this should be called `remove-single-property' like
1122 ;; `next-single-property-change' (not `next-single-text-property-change'), etc.
1123 ;(defun remove-single-text-property (start end prop value &optional object)
1124 ; "Remove a specific property value from text from START to END.
1125 ;Arguments PROP and VALUE specify the property and value to remove. The
1126 ;resulting property values are not equal to VALUE nor lists containing VALUE.
1127 ;Optional argument OBJECT is the string or buffer containing the text."
1128 ; (let ((start (text-property-not-all start end prop nil object)) next prev)
1129 ; (while start
1130 ; (setq next (next-single-property-change start prop object end)
1131 ; prev (get-text-property start prop object))
1132 ; (cond ((and (symbolp prev) (eq value prev))
1133 ; (remove-text-property start next prop object))
1134 ; ((and (listp prev) (memq value prev))
1135 ; (let ((new (delq value prev)))
1136 ; (cond ((null new)
1137 ; (remove-text-property start next prop object))
1138 ; ((= (length new) 1)
1139 ; (put-text-property start next prop (car new) object))
1140 ; (t
1141 ; (put-text-property start next prop new object))))))
1142 ; (setq start (text-property-not-all next end prop nil object)))))
1144 ;;; End of Additional text property functions.
1145 \f
1146 ;;; Syntactic regexp fontification functions.
1148 ;; These syntactic keyword pass functions are identical to those keyword pass
1149 ;; functions below, with the following exceptions; (a) they operate on
1150 ;; `font-lock-syntactic-keywords' of course, (b) they are all `defun' as speed
1151 ;; is less of an issue, (c) eval of property value does not occur JIT as speed
1152 ;; is less of an issue, (d) OVERRIDE cannot be `prepend' or `append' as it
1153 ;; makes no sense for `syntax-table' property values, (e) they do not do it
1154 ;; LOUDLY as it is not likely to be intensive.
1157 "Apply HIGHLIGHT following a match.
1158 HIGHLIGHT should be of the form MATCH-HIGHLIGHT,
1159 see `font-lock-syntactic-keywords'."
1165 ;; No match but we might not signal an error.
1171 ;; Flush the syntax-cache. I believe this is not necessary for
1172 ;; font-lock's use of syntax-ppss, but I'm not 100% sure and it can
1173 ;; still be necessary for other users of syntax-ppss anyway.
1177 ;; Cannot override existing fontification.
1181 ;; Override existing fontification.
1184 ;; Keep existing fontification.
1188 "Fontify according to KEYWORDS until LIMIT.
1189 KEYWORDS should be of the form MATCH-ANCHORED, see `font-lock-keywords',
1190 LIMIT can be modified by the value of its PRE-MATCH-FORM."
1192 ;; Evaluate PRE-MATCH-FORM.
1194 ;; Set LIMIT to value of PRE-MATCH-FORM or the end of line.
1199 ;; Find an occurrence of `matcher' before `limit'.
1203 ;; Apply each highlight to this instance of `matcher'.
1208 ;; Evaluate POST-MATCH-FORM.
1212 "Fontify according to `font-lock-syntactic-keywords' between START and END.
1213 START should be at the beginning of a line."
1214 ;; Ensure the beginning of the file is properly syntactic-fontified.
1219 ;; If `font-lock-syntactic-keywords' is a symbol, get the real keywords.
1222 font-lock-syntactic-keywords)))
1223 ;; If `font-lock-syntactic-keywords' is not compiled, compile it.
1226 font-lock-syntactic-keywords)))
1227 ;; Get down to business.
1230 keyword matcher highlights)
1232 ;; Find an occurrence of `matcher' from `start' to `end'.
1238 ;; Apply each highlight to this instance of `matcher', which may be
1239 ;; specific highlights or more keywords anchored to `matcher'.
1245 end))
1249 ;;; End of Syntactic regexp fontification functions.
1250 \f
1251 ;;; Syntactic fontification functions.
1254 "Put proper face on each string and comment between START and END.
1255 START should be at the beginning of a line."
1259 ;;
1260 ;; Find the state at the `beginning-of-line' before `start'.
1262 ;;
1263 ;; Find each interesting place between here and `end'.
1276 ;;; End of Syntactic fontification functions.
1277 \f
1278 ;;; Keyword regexp fontification functions.
1281 "Apply HIGHLIGHT following a match.
1282 HIGHLIGHT should be of the form MATCH-HIGHLIGHT, see `font-lock-keywords'."
1287 ;; No match but we might not signal an error.
1296 ;; Cannot override existing fontification.
1300 ;; Override existing fontification.
1303 ;; Prepend to existing fontification.
1306 ;; Append to 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."
1318 ;; Evaluate PRE-MATCH-FORM.
1320 ;; Set LIMIT to value of PRE-MATCH-FORM or the end of line.
1325 ;; this is a multiline anchored match
1326 ;; (setq font-lock-multiline t)
1330 limit
1333 ;; Find an occurrence of `matcher' before `limit'.
1338 ;; Apply each highlight to this instance of `matcher'.
1343 ;; Evaluate POST-MATCH-FORM.
1347 "Fontify according to `font-lock-keywords' between START and END.
1348 START should be at the beginning of a line.
1349 LOUDLY, if non-nil, allows progress-meter bar."
1356 keyword matcher highlights)
1357 ;;
1358 ;; Fontify each item in `font-lock-keywords' from `start' to `end'.
1362 ;;
1363 ;; Find an occurrence of `matcher' from `start' to `end'.
1374 ;; this is a multiline regexp match
1375 ;; (setq font-lock-multiline t)
1384 ;; Apply each highlight to this instance of `matcher', which may be
1385 ;; specific highlights or more keywords anchored to `matcher'.
1394 ;;; End of Keyword regexp fontification functions.
1395 \f
1396 ;; Various functions.
1399 "Compile KEYWORDS into the form (t KEYWORD ...).
1400 Here KEYWORD is of the form (MATCHER HIGHLIGHT ...) as shown in the
1401 `font-lock-keywords' doc string.
1402 If REGEXP is non-nil, it means these keywords are used for
1403 `font-lock-keywords' rather than for `font-lock-syntactic-keywords'."
1405 keywords
1409 font-lock-beginning-of-syntax-function)
1412 ;; Try to detect when a string or comment contains something that
1413 ;; looks like a defun and would thus confuse font-lock.
1421 font-lock-comment-face))
1422 font-lock-warning-face)
1423 prepend)))))
1424 keywords))
1432 ;; If FORM is a FACENAME then quote it. Otherwise ignore the quote.
1443 keyword)))
1446 "Evalulate KEYWORDS if a function (funcall) or variable (eval) name."
1448 keywords
1454 "Return value in ALIST for `major-mode', or ALIST if it is not an alist.
1455 Structure is ((MAJOR-MODE . VALUE) ...) where MAJOR-MODE may be t."
1458 alist))
1461 "Return LEVELth element of KEYWORDS.
1462 A LEVEL of nil is equal to a LEVEL of 0, a LEVEL of t is equal to
1463 \(1- (length KEYWORDS))."
1465 keywords)
1476 "Set fontification defaults appropriately for this mode.
1477 Sets various variables using `font-lock-defaults' (or, if nil, using
1478 `font-lock-defaults-alist') and `font-lock-maximum-decoration'."
1479 ;; Set fontification defaults iff not previously set.
1493 ;; Syntactic fontification?
1496 ;; Case fold during regexp fontification?
1499 ;; Syntax table for regexp and syntactic fontification?
1504 ;; The character to modify may be a single CHAR or a STRING.
1510 ;; Syntax function for syntactic fontification?
1514 ;; Variable alist?
1517 ;; Setup `font-lock-keywords' last because its value might depend
1518 ;; on other settings (e.g. font-lock-compile-keywords uses
1519 ;; font-lock-beginning-of-syntax-function).
1522 ;; Local fontification?
1528 \f
1529 ;;; Colour etc. support.
1531 ;; Originally face attributes were specified via `font-lock-face-attributes'.
1532 ;; Users then changed the default face attributes by setting that variable.
1533 ;; However, we try and be back-compatible and respect its value if set except
1534 ;; for faces where M-x customize has been used to save changes for the face.
1540 ;; Rustle up a `defface' SPEC from a `font-lock-face-attributes' entry.
1547 face-spec)
1560 ;; But now we do it the custom way. Note that `defface' will not overwrite any
1561 ;; faces declared above via `custom-declare-face'.
1580 "Font Lock mode face used to highlight comments."
1592 "Font Lock mode face used to highlight strings."
1597 "Font Lock mode face used to highlight documentation."
1609 "Font Lock mode face used to highlight keywords."
1621 "Font Lock mode face used to highlight builtins."
1631 "Font Lock mode face used to highlight function names."
1645 "Font Lock mode face used to highlight variable names."
1657 "Font Lock mode face used to highlight type and classes."
1671 "Font Lock mode face used to highlight constants and labels."
1678 (((class color) (min-colors 16) (background dark)) (:foreground "Pink" :weight bold)) (((class color) (min-colors 8)) (:foreground "red"))
1680 "Font Lock mode face used to highlight warnings."
1685 "Font Lock mode face used to highlight preprocessor directives."
1688 ;;; End of Colour etc. support.
1689 \f
1690 ;;; Menu support.
1692 ;; This section of code is commented out because Emacs does not have real menu
1693 ;; buttons. (We can mimic them by putting "( ) " or "(X) " at the beginning of
1694 ;; the menu entry text, but with Xt it looks both ugly and embarrassingly
1695 ;; amateur.) If/When Emacs gets real menus buttons, put in menu-bar.el after
1696 ;; the entry for "Text Properties" something like:
1697 ;;
1698 ;; (define-key menu-bar-edit-menu [font-lock]
1699 ;; (cons "Syntax Highlighting" font-lock-menu))
1700 ;;
1701 ;; and remove a single ";" from the beginning of each line in the rest of this
1702 ;; section. Probably the mechanism for telling the menu code what are menu
1703 ;; buttons and when they are on or off needs tweaking. I have assumed that the
1704 ;; mechanism is via `menu-toggle' and `menu-selected' symbol properties. sm.
1706 ;;;;###autoload
1707 ;(progn
1708 ; ;; Make the Font Lock menu.
1709 ; (defvar font-lock-menu (make-sparse-keymap "Syntax Highlighting"))
1710 ; ;; Add the menu items in reverse order.
1711 ; (define-key font-lock-menu [fontify-less]
1712 ; '("Less In Current Buffer" . font-lock-fontify-less))
1713 ; (define-key font-lock-menu [fontify-more]
1714 ; '("More In Current Buffer" . font-lock-fontify-more))
1715 ; (define-key font-lock-menu [font-lock-sep]
1716 ; '("--"))
1717 ; (define-key font-lock-menu [font-lock-mode]
1718 ; '("In Current Buffer" . font-lock-mode))
1719 ; (define-key font-lock-menu [global-font-lock-mode]
1720 ; '("In All Buffers" . global-font-lock-mode)))
1721 ;
1722 ;;;;###autoload
1723 ;(progn
1724 ; ;; We put the appropriate `menu-enable' etc. symbol property values on when
1725 ; ;; font-lock.el is loaded, so we don't need to autoload the three variables.
1726 ; (put 'global-font-lock-mode 'menu-toggle t)
1727 ; (put 'font-lock-mode 'menu-toggle t)
1728 ; (put 'font-lock-fontify-more 'menu-enable '(identity))
1729 ; (put 'font-lock-fontify-less 'menu-enable '(identity)))
1730 ;
1731 ;;; Put the appropriate symbol property values on now. See above.
1732 ;(put 'global-font-lock-mode 'menu-selected 'global-font-lock-mode)
1733 ;(put 'font-lock-mode 'menu-selected 'font-lock-mode)
1734 ;(put 'font-lock-fontify-more 'menu-enable '(nth 2 font-lock-fontify-level))
1735 ;(put 'font-lock-fontify-less 'menu-enable '(nth 1 font-lock-fontify-level))
1736 ;
1737 ;(defvar font-lock-fontify-level nil) ; For less/more fontification.
1738 ;
1739 ;(defun font-lock-fontify-level (level)
1740 ; (let ((font-lock-maximum-decoration level))
1741 ; (when font-lock-mode
1742 ; (font-lock-mode))
1743 ; (font-lock-mode)
1744 ; (when font-lock-verbose
1745 ; (message "Fontifying %s... level %d" (buffer-name) level))))
1746 ;
1747 ;(defun font-lock-fontify-less ()
1748 ; "Fontify the current buffer with less decoration.
1749 ;See `font-lock-maximum-decoration'."
1750 ; (interactive)
1751 ; ;; Check in case we get called interactively.
1752 ; (if (nth 1 font-lock-fontify-level)
1753 ; (font-lock-fontify-level (1- (car font-lock-fontify-level)))
1754 ; (error "No less decoration")))
1755 ;
1756 ;(defun font-lock-fontify-more ()
1757 ; "Fontify the current buffer with more decoration.
1758 ;See `font-lock-maximum-decoration'."
1759 ; (interactive)
1760 ; ;; Check in case we get called interactively.
1761 ; (if (nth 2 font-lock-fontify-level)
1762 ; (font-lock-fontify-level (1+ (car font-lock-fontify-level)))
1763 ; (error "No more decoration")))
1764 ;
1765 ;;; This should be called by `font-lock-set-defaults'.
1766 ;(defun font-lock-set-menu ()
1767 ; ;; Activate less/more fontification entries if there are multiple levels for
1768 ; ;; the current buffer. Sets `font-lock-fontify-level' to be of the form
1769 ; ;; (CURRENT-LEVEL IS-LOWER-LEVEL-P IS-HIGHER-LEVEL-P) for menu activation.
1770 ; (let ((keywords (or (nth 0 font-lock-defaults)
1771 ; (nth 1 (assq major-mode font-lock-defaults-alist))))
1772 ; (level (font-lock-value-in-major-mode font-lock-maximum-decoration)))
1773 ; (make-local-variable 'font-lock-fontify-level)
1774 ; (if (or (symbolp keywords) (= (length keywords) 1))
1775 ; (font-lock-unset-menu)
1776 ; (cond ((eq level t)
1777 ; (setq level (1- (length keywords))))
1778 ; ((or (null level) (zerop level))
1779 ; ;; The default level is usually, but not necessarily, level 1.
1780 ; (setq level (- (length keywords)
1781 ; (length (member (eval (car keywords))
1782 ; (mapcar 'eval (cdr keywords))))))))
1783 ; (setq font-lock-fontify-level (list level (> level 1)
1784 ; (< level (1- (length keywords))))))))
1785 ;
1786 ;;; This should be called by `font-lock-unset-defaults'.
1787 ;(defun font-lock-unset-menu ()
1788 ; ;; Deactivate less/more fontification entries.
1789 ; (setq font-lock-fontify-level nil))
1791 ;;; End of Menu support.
1792 \f
1793 ;;; Various regexp information shared by several modes.
1794 ;;; Information specific to a single mode should go in its load library.
1796 ;; Font Lock support for C, C++, Objective-C and Java modes is now in
1797 ;; cc-fonts.el (and required by cc-mode.el). However, the below function
1798 ;; should stay in font-lock.el, since it is used by other libraries. sm.
1801 "Match, and move over, any declaration/definition item after point.
1802 Matches after point, but ignores leading whitespace and `*' characters.
1803 Does not move further than LIMIT.
1805 The expected syntax of a declaration/definition item is `word' (preceded by
1806 optional whitespace and `*' characters and proceeded by optional whitespace)
1807 optionally followed by a `('. Everything following the item (but belonging to
1808 it) is expected to be skip-able by `scan-sexps', and items are expected to be
1809 separated with a `,' and to be terminated with a `;'.
1811 Thus the regexp matches after point: word (
1812 ^^^^ ^
1813 Where the match subexpressions are: 1 2
1815 The item is delimited by (match-beginning 1) and (match-end 1).
1816 If (match-beginning 2) is non-nil, the item is followed by a `('.
1818 This function could be MATCHER in a MATCH-ANCHORED `font-lock-keywords' item."
1821 ;; If `word' is followed by a double open-paren, it's probably
1822 ;; a macro used for "int myfun P_ ((int arg1))". Let's go back one
1823 ;; word to try and match `myfun' rather than `P_'.
1828 ;; Looks like it was something else, so go back to where we
1829 ;; were and reset the match data by rematching.
1835 ;; Restrict to the LIMIT.
1838 ;; Move over any item value, etc., to the next item.
1843 \f
1844 ;; Lisp.
1849 ;;
1850 ;; Definitions.
1852 ;; Function declarations.
1858 ;; Variable declarations.
1860 ;; Structure declarations.
1863 ;; Any whitespace and defined object.
1870 nil t))
1871 ;;
1872 ;; Emacs Lisp autoload cookies.
1874 ))
1881 ;;
1882 ;; Control structures. Emacs Lisp forms.
1892 "eval-when"
1893 "with-category-table"
1902 ;;
1903 ;; Control structures. Common Lisp forms.
1923 ;;
1924 ;; Exit/Feature symbols as constants.
1929 ;;
1930 ;; Erroneous structures.
1932 ;;
1933 ;; Words inside \\[] tend to be for `substitute-command-keys'.
1935 ;;
1936 ;; Words inside `' tend to be symbol names.
1938 ;;
1939 ;; Constant values.
1941 ;;
1942 ;; ELisp and CLisp `&' keywords as types.
1944 ;;
1945 ;;; This is too general -- rms.
1946 ;;; A user complained that he has functions whose names start with `do'
1947 ;;; and that they get the wrong color.
1948 ;;; ;; CL `with-' and `do-' constructs
1949 ;;; '("(\\(\\(do-\\|with-\\)\\(\\s_\\|\\w\\)*\\)" 1 font-lock-keyword-face)
1950 )))
1955 \f
1958 ;;; arch-tag: 682327e4-64d8-4057-b20b-1fbb9f1fc54c
1959 ;;; font-lock.el ends here