| blob | 032b8fb04f8efa9058bb61fb632a30bea81d606d |
1 ;;; font-lock.el --- Electric font lock mode
3 ;; Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
4 ;; 2000, 2001, 2002, 2003, 2004, 2005, 2006 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., 51 Franklin Street, Fifth Floor,
25 ;; Boston, MA 02110-1301, 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 ;; (set (make-local-variable 'font-lock-defaults)
157 ;; '(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 ;; (set (make-local-variable 'font-lock-defaults)
178 ;; '(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."
227 \f
228 ;; User variables.
231 "*Maximum size of a buffer for buffer fontification.
232 Only buffers less than this can be fontified when Font Lock mode is turned on.
233 If nil, means size is irrelevant.
234 If a list, each element should be a cons pair of the form (MAJOR-MODE . SIZE),
235 where MAJOR-MODE is a symbol or t (meaning the default). For example:
236 ((c-mode . 256000) (c++-mode . 256000) (rmail-mode . 1048576))
237 means that the maximum size is 250K for buffers in C or C++ modes, one megabyte
238 for buffers in Rmail mode, and size is irrelevant otherwise."
253 "*Maximum decoration level for fontification.
254 If nil, use the default decoration (typically the minimum available).
255 If t, use the maximum decoration available.
256 If a number, use that level of decoration (or if not available the maximum).
257 If a list, each element should be a cons pair of the form (MAJOR-MODE . LEVEL),
258 where MAJOR-MODE is a symbol or t (meaning the default). For example:
259 ((c-mode . t) (c++-mode . 2) (t . 1))
260 means use the maximum decoration available for buffers in C mode, level 2
261 decoration for buffers in C++ mode, and level 1 decoration otherwise."
278 "*If non-nil, means show status messages for buffer fontification.
279 If a number, only buffers greater than this size have fontification messages."
286 "*Number of lines before the changed text to include in refontification."
290 \f
292 ;; Originally these variable values were face names such as `bold' etc.
293 ;; Now we create our own faces, but we keep these variables for compatibility
294 ;; and they give users another mechanism for changing face appearance.
295 ;; We now allow a FACENAME in `font-lock-keywords' to be any expression that
296 ;; returns a face. So the easiest thing is to continue using these variables,
297 ;; rather than sometimes evaling FACENAME and sometimes not. sm.
332 "Face name to use for easy to overlook negation.
341 ;; Fontification variables:
344 "A list of the keywords to highlight.
345 There are two kinds of values: user-level, and compiled.
347 A user-level keywords list is what a major mode or the user would
348 set up. Normally the list would come from `font-lock-defaults'.
349 through selection of a fontification level and evaluation of any
350 contained expressions. You can also alter it by calling
351 `font-lock-add-keywords' or `font-lock-remove-keywords' with MODE = nil.
353 Each element in a user-level keywords list should have one of these forms:
355 MATCHER
356 (MATCHER . SUBEXP)
357 (MATCHER . FACENAME)
358 (MATCHER . HIGHLIGHT)
359 (MATCHER HIGHLIGHT ...)
360 (eval . FORM)
362 where MATCHER can be either the regexp to search for, or the function name to
363 call to make the search (called with one argument, the limit of the search;
364 it should return non-nil, move point, and set `match-data' appropriately iff
365 it succeeds; like `re-search-forward' would).
366 MATCHER regexps can be generated via the function `regexp-opt'.
368 FORM is an expression, whose value should be a keyword element, evaluated when
369 the keyword is (first) used in a buffer. This feature can be used to provide a
370 keyword that can only be generated when Font Lock mode is actually turned on.
372 HIGHLIGHT should be either MATCH-HIGHLIGHT or MATCH-ANCHORED.
375 typically only MATCH-HIGHLIGHT is required.
376 However, if an item or (typically) items are to be highlighted following the
377 instance of another item (the anchor), for example each instance of the
380 MATCH-HIGHLIGHT should be of the form:
382 (SUBEXP FACENAME [OVERRIDE [LAXMATCH]])
384 SUBEXP is the number of the subexpression of MATCHER to be highlighted.
386 FACENAME is an expression whose value is the face name to use.
387 Instead of a face, FACENAME can evaluate to a property list
388 of the form (face FACE PROP1 VAL1 PROP2 VAL2 ...)
389 in which case all the listed text-properties will be set rather than
390 just FACE. In such a case, you will most likely want to put those
391 properties in `font-lock-extra-managed-props' or to override
392 `font-lock-unfontify-region-function'.
394 OVERRIDE and LAXMATCH are flags. If OVERRIDE is t, existing fontification can
395 be overwritten. If `keep', only parts not already fontified are highlighted.
396 If `prepend' or `append', existing fontification is merged with the new, in
397 which the new or existing fontification, respectively, takes precedence.
398 If LAXMATCH is non-nil, that means don't signal an error if there is
399 no match for SUBEXP in MATCHER.
401 For example, an element of the form highlights (if not already highlighted):
404 variable `font-lock-keyword-face'.
406 the value of `font-lock-keyword-face'.
410 of `foo-bar-face', even if already highlighted.
411 (fubar-match 1 fubar-face)
412 the first subexpression within all occurrences of
413 whatever the function `fubar-match' finds and matches
414 in the value of `fubar-face'.
416 MATCH-ANCHORED should be of the form:
418 (MATCHER PRE-MATCH-FORM POST-MATCH-FORM MATCH-HIGHLIGHT ...)
420 where MATCHER is a regexp to search for or the function name to call to make
421 the search, as for MATCH-HIGHLIGHT above, but with one exception; see below.
422 PRE-MATCH-FORM and POST-MATCH-FORM are evaluated before the first, and after
423 the last, instance MATCH-ANCHORED's MATCHER is used. Therefore they can be
424 used to initialize before, and cleanup after, MATCHER is used. Typically,
425 PRE-MATCH-FORM is used to move to some position relative to the original
426 MATCHER, before starting with MATCH-ANCHORED's MATCHER. POST-MATCH-FORM might
427 be used to move back, before resuming with MATCH-ANCHORED's parent's MATCHER.
429 For example, an element of the form highlights (if not already highlighted):
440 The above-mentioned exception is as follows. The limit of the MATCHER search
441 defaults to the end of the line after PRE-MATCH-FORM is evaluated.
442 However, if PRE-MATCH-FORM returns a position greater than the position after
443 PRE-MATCH-FORM is evaluated, that position is used as the limit of the search.
444 It is generally a bad idea to return a position greater than the end of the
445 line, i.e., cause the MATCHER search to span lines.
447 These regular expressions can match text which spans lines, although
448 it is better to avoid it if possible since updating them while editing
449 text is slower, and it is not guaranteed to be always correct when using
450 support modes like jit-lock or lazy-lock.
452 This variable is set by major modes via the variable `font-lock-defaults'.
453 Be careful when composing regexps for this list; a poorly written pattern can
454 dramatically slow things down!
456 A compiled keywords list starts with t. It is produced internal
457 by `font-lock-compile-keywords' from a user-level keywords list.
458 Its second element is the user-level keywords list that was
459 compiled. The remaining elements have the same form as
460 user-level keywords, but normally their values have been
464 "Alist of additional `font-lock-keywords' elements for major modes.
466 Each element has the form (MODE KEYWORDS . HOW).
467 `font-lock-set-defaults' adds the elements in the list KEYWORDS to
468 `font-lock-keywords' when Font Lock is turned on in major mode MODE.
470 If HOW is nil, KEYWORDS are added at the beginning of
471 `font-lock-keywords'. If it is `set', they are used to replace the
472 value of `font-lock-keywords'. If HOW is any other non-nil value,
473 they are added at the end.
475 This is normally set via `font-lock-add-keywords' and
479 "Alist of `font-lock-keywords' elements to be removed for major modes.
481 Each element has the form (MODE . KEYWORDS). `font-lock-set-defaults'
482 removes the elements in the list KEYWORDS from `font-lock-keywords'
483 when Font Lock is turned on in major mode MODE.
485 This is normally set via `font-lock-add-keywords' and
489 "*Non-nil means Font Lock should not fontify comments or strings.
493 "*Non-nil means the patterns in `font-lock-keywords' are case-insensitive.
498 "Point up to which `font-lock-syntactic-keywords' has been applied.
499 If nil, this is ignored, in which case the syntactic fontification may
506 "Function to determine which face to use when fontifying syntactically.
507 The function is called with a single parameter (the state as returned by
508 `parse-partial-sexp' at the beginning of the region to highlight) and
512 "A list of the syntactic keywords to put syntax properties on.
513 The value can be the list itself, or the name of a function or variable
514 whose value is the list.
516 See `font-lock-keywords' for a description of the form of this list;
517 only the differences are stated here. MATCH-HIGHLIGHT should be of the form:
519 (SUBEXP SYNTAX OVERRIDE LAXMATCH)
521 where SYNTAX can be a string (as taken by `modify-syntax-entry'), a syntax
522 table, a cons cell (as returned by `string-to-syntax') or an expression whose
523 value is such a form. OVERRIDE cannot be `prepend' or `append'.
525 Here are two examples of elements of `font-lock-syntactic-keywords'
526 and what they do:
531 dollar-sign character. Hash characters in other contexts will still
532 follow whatever the syntax table says about the hash character.
538 gives a pair single-quotes, which surround a single character, a SYNTAX of
540 contexts will not be affected.
545 "Non-nil means use this syntax table for fontifying.
546 If this is nil, the major mode's syntax table is used.
550 "*Non-nil means use this function to move back outside all constructs.
551 When called with no args it should move point backward to a place which
552 is not in a string or comment and not within any bracket-pairs (or else,
553 a place such that any bracket-pairs outside it can be ignored for Emacs
554 syntax analysis and fontification).
556 If this is nil, Font Lock uses `syntax-begin-function' to move back
557 outside of any comment, string, or sexp. This variable is semi-obsolete;
558 we recommend setting `syntax-begin-function' instead.
563 "*Non-nil means use this function to mark a block of text.
564 When called with no args it should leave point at the beginning of any
565 enclosing textual block and mark at the end.
569 "Function to use for fontifying the buffer.
573 "Function to use for unfontifying the buffer.
574 This is used when turning off Font Lock mode.
578 "Function to use for fontifying a region.
579 It should take two args, the beginning and end of the region, and an optional
580 third arg VERBOSE. If VERBOSE is non-nil, the function should print status
584 "Function to use for unfontifying a region.
585 It should take two args, the beginning and end of the region.
589 "List of Font Lock mode related modes that should not be turned on.
590 Currently, valid mode names are `fast-lock-mode', `jit-lock-mode' and
594 "Whether font-lock should cater to multiline keywords.
595 If nil, don't try to handle multiline patterns.
596 If t, always handle multiline patterns.
597 If `undecided', don't try to handle multiline patterns until you see one.
601 \f
602 ;; Font Lock mode.
605 ;;
606 ;; We don't do this at the top-level as we only use non-autoloaded macros.
608 ;;
609 ;; Borrowed from lazy-lock.el.
610 ;; We use this to preserve or protect things when modifying text properties.
612 "Bind variables according to VARLIST and eval BODY restoring buffer state."
621 deactivate-mark
622 buffer-file-name
623 buffer-file-truename))
628 ;;
629 ;; Shut up the byte compiler.
633 ;; Turn on Font Lock mode.
638 ;; Fontify the buffer if we have to.
641 nil)
647 ;; Turn off Font Lock mode.
654 "Add highlighting KEYWORDS for MODE.
656 MODE should be a symbol, the major mode command name, such as `c-mode'
657 or nil. If nil, highlighting keywords are added for the current buffer.
658 KEYWORDS should be a list; see the variable `font-lock-keywords'.
659 By default they are added at the beginning of the current highlighting list.
660 If optional argument HOW is `set', they are used to replace the current
661 highlighting list. If HOW is any other non-nil value, they are added at the
662 end of the current highlighting list.
664 For example:
666 (font-lock-add-keywords 'c-mode
670 adds two fontification patterns for C mode, to fontify `FIXME:' words, even in
671 comments, and to fontify `and', `or' and `not' words as keywords.
673 The above procedure will only add the keywords for C mode, not
674 for modes derived from C mode. To add them for derived modes too,
675 pass nil for MODE and add the call to c-mode-hook.
677 For example:
679 (add-hook 'c-mode-hook
680 (lambda ()
681 (font-lock-add-keywords nil
684 font-lock-keyword-face)))))
686 The above procedure may fail to add keywords to derived modes if
687 some involved major mode does not follow the standard conventions.
688 File a bug report if this happens, so the major mode can be corrected.
690 Note that some modes have specialized support for additional patterns, e.g.,
691 see the variables `c-font-lock-extra-types', `c++-font-lock-extra-types',
692 `objc-font-lock-extra-types' and `java-font-lock-extra-types'."
694 ;; If MODE is non-nil, add the KEYWORDS and HOW spec to
695 ;; `font-lock-keywords-alist' so `font-lock-set-defaults' uses them.
702 ;; Make sure that `font-lock-removed-keywords-alist' does not
703 ;; contain the new keywords.
706 ;; Otherwise set or add the keywords now.
707 ;; This is a no-op if it has been done already in this buffer
708 ;; for the correct major mode.
711 ;; Bring back the user-level (uncompiled) keywords.
714 ;; Now modify or replace them.
720 font-lock-keywords)))
724 ;; If the keywords were compiled before, compile them again.
730 "Update `font-lock-removed-keywords-alist' when adding new KEYWORDS to MODE."
731 ;; When font-lock is enabled first all keywords in the list
732 ;; `font-lock-keywords-alist' are added, then all keywords in the
733 ;; list `font-lock-removed-keywords-alist' are removed. If a
734 ;; keyword was once added, removed, and then added again it must be
735 ;; removed from the removed-keywords list. Otherwise the second add
736 ;; will not take effect.
740 ;; A new set of keywords is defined. Forget all about
741 ;; our old keywords that should be removed.
744 ;; Delete all previously removed keywords.
747 ;; Delete the mode cell if empty.
752 ;; Written by Anders Lindgren <andersl@andersl.com>.
753 ;;
754 ;; Case study:
755 ;; (I) The keywords are removed from a major mode.
756 ;; In this case the keyword could be local (i.e. added earlier by
757 ;; `font-lock-add-keywords'), global, or both.
758 ;;
759 ;; (a) In the local case we remove the keywords from the variable
760 ;; `font-lock-keywords-alist'.
761 ;;
762 ;; (b) The actual global keywords are not known at this time.
763 ;; All keywords are added to `font-lock-removed-keywords-alist',
764 ;; when font-lock is enabled those keywords are removed.
765 ;;
766 ;; Note that added keywords are taken out of the list of removed
767 ;; keywords. This ensure correct operation when the same keyword
768 ;; is added and removed several times.
769 ;;
770 ;; (II) The keywords are removed from the current buffer.
772 "Remove highlighting KEYWORDS for MODE.
774 MODE should be a symbol, the major mode command name, such as `c-mode'
775 or nil. If nil, highlighting keywords are removed for the current buffer.
777 To make the removal apply to modes derived from MODE as well,
778 pass nil for MODE and add the call to MODE-hook. This may fail
779 for some derived modes if some involved major mode does not
780 follow the standard conventions. File a bug report if this
781 happens, so the major mode can be corrected."
783 ;; Remove one keyword at the time.
786 ;; If MODE is non-nil, remove the KEYWORD from
787 ;; `font-lock-keywords-alist'.
790 ;; `keywords-list-how-pair' is a cons with a list of
791 ;; keywords in the car top-cell and the original how
792 ;; argument in the cdr top-cell.
795 ;; Remove keyword list/how pair when the keyword list
796 ;; is empty and how doesn't specify `set'. (If it
797 ;; should be deleted then previously deleted keywords
798 ;; would appear again.)
805 ;; Final cleanup, remove major mode cell if last keyword
806 ;; was deleted.
810 ;; Remember the keyword in case it is not local.
816 font-lock-removed-keywords-alist))))))
818 ;; Otherwise remove it immediately.
821 ;; Bring back the user-level (uncompiled) keywords.
825 ;; Edit them.
831 ;; If the keywords were compiled before, compile them again.
835 \f
836 ;;; Font Lock Support mode.
838 ;; This is the code used to interface font-lock.el with any of its add-on
839 ;; packages, and provide the user interface. Packages that have their own
840 ;; local buffer fontification functions (see below) may have to call
841 ;; `font-lock-after-fontify-buffer' and/or `font-lock-after-unfontify-buffer'
842 ;; themselves.
845 "*Support mode for Font Lock mode.
846 Support modes speed up Font Lock mode by being choosy about when fontification
847 occurs. The default support mode, Just-in-time Lock mode (symbol
848 `jit-lock-mode'), is recommended.
850 Other, older support modes are Fast Lock mode (symbol `fast-lock-mode') and
851 Lazy Lock mode (symbol `lazy-lock-mode'). See those modes for more info.
852 However, they are no longer recommended, as Just-in-time Lock mode is better.
854 If nil, means support for Font Lock mode is never performed.
855 If a symbol, use that support mode.
856 If a list, each element should be of the form (MAJOR-MODE . SUPPORT-MODE),
857 where MAJOR-MODE is a symbol or t (meaning the default). For example:
858 ((c-mode . fast-lock-mode) (c++-mode . fast-lock-mode) (t . lazy-lock-mode))
859 means that Fast Lock mode is used to support Font Lock mode for buffers in C or
860 C++ modes, and Lazy Lock mode is used to support Font Lock mode otherwise.
862 The value of this variable is used when Font Lock mode is turned on."
878 ))
893 ;; Prepare for jit-lock
898 ;; Don't fontify eagerly (and don't abort if the buffer is large).
900 ;; Use jit-lock.
909 ;; Reset local vars to the non-jit-lock case.
917 ;; Useless now that jit-lock intercepts font-lock-fontify-buffer. -sm
918 ;; (jit-lock-mode
919 ;; (jit-lock-after-fontify-buffer))
926 ;; Useless as well. It's only called when:
927 ;; - turning off font-lock: it does not matter if we leave spurious
928 ;; `fontified' text props around since jit-lock-mode is also off.
929 ;; - font-lock-default-fontify-buffer fails: this is not run
930 ;; any more anyway. -sm
931 ;;
932 ;; (jit-lock-mode
933 ;; (jit-lock-after-unfontify-buffer))
937 ;;; End of Font Lock Support mode.
938 \f
939 ;;; Fontification functions.
941 ;; Rather than the function, e.g., `font-lock-fontify-region' containing the
942 ;; code to fontify a region, the function runs the function whose name is the
943 ;; value of the variable, e.g., `font-lock-fontify-region-function'. Normally,
944 ;; the value of this variable is, e.g., `font-lock-default-fontify-region'
945 ;; which does contain the code to fontify a region. However, the value of the
946 ;; variable could be anything and thus, e.g., `font-lock-fontify-region' could
947 ;; do anything. The indirection of the fontification functions gives major
948 ;; modes the capability of modifying the way font-lock.el fontifies. Major
949 ;; modes can modify the values of, e.g., `font-lock-fontify-region-function',
950 ;; via the variable `font-lock-defaults'.
951 ;;
952 ;; For example, Rmail mode sets the variable `font-lock-defaults' so that
953 ;; font-lock.el uses its own function for buffer fontification. This function
954 ;; makes fontification be on a message-by-message basis and so visiting an
955 ;; RMAIL file is much faster. A clever implementation of the function might
956 ;; fontify the headers differently than the message body. (It should, and
957 ;; correspondingly for Mail mode, but I can't be bothered to do the work. Can
958 ;; you?) This hints at a more interesting use...
959 ;;
960 ;; Languages that contain text normally contained in different major modes
961 ;; could define their own fontification functions that treat text differently
962 ;; depending on its context. For example, Perl mode could arrange that here
963 ;; docs are fontified differently than Perl code. Or Yacc mode could fontify
964 ;; rules one way and C code another. Neat!
965 ;;
966 ;; A further reason to use the fontification indirection feature is when the
967 ;; default syntactual fontification, or the default fontification in general,
968 ;; is not flexible enough for a particular major mode. For example, perhaps
969 ;; comments are just too hairy for `font-lock-fontify-syntactically-region' to
970 ;; cope with. You need to write your own version of that function, e.g.,
971 ;; `hairy-fontify-syntactically-region', and make your own version of
972 ;; `hairy-fontify-region' call that function before calling
973 ;; `font-lock-fontify-keywords-region' for the normal regexp fontification
974 ;; pass. And Hairy mode would set `font-lock-defaults' so that font-lock.el
975 ;; would call your region fontification function instead of its own. For
976 ;; example, TeX modes could fontify {\foo ...} and \bar{...} etc. multi-line
977 ;; directives correctly and cleanly. (It is the same problem as fontifying
978 ;; multi-line strings and comments; regexps are not appropriate for the job.)
981 "Fontify the current buffer the way the function `font-lock-mode' would."
1001 font-lock-verbose)))
1005 ;; Make sure we fontify etc. in the whole buffer.
1014 ;; We don't restore the old fontification, so it's best to unfontify.
1018 ;; Make sure we unfontify etc. in the whole buffer.
1026 "If non-nil, font-lock will work on the non-widened buffer.
1027 Useful for things like RMAIL and Info where the whole buffer is not
1038 ;; Use the fontification syntax table, if any.
1043 ;; check to see if we should expand the beg/end area for
1044 ;; proper multiline matches
1047 ;; We are just after or in a multiline match.
1057 ;; Round up to a whole line.
1059 ;; Now do the fontification.
1066 ;; Clean up.
1069 ;; The following must be rethought, since keywords can override fontification.
1070 ;; ;; Now scan for keywords, but not if we are inside a comment now.
1071 ;; (or (and (not font-lock-keywords-only)
1072 ;; (let ((state (parse-partial-sexp beg end nil nil
1073 ;; font-lock-cache-state)))
1074 ;; (or (nth 4 state) (nth 7 state))))
1075 ;; (font-lock-fontify-keywords-region beg end))
1078 "Additional text properties managed by font-lock.
1079 This is used by `font-lock-default-unfontify-region' to decide
1085 font-lock-extra-managed-props
1090 ;; Called when any modification is made to buffer text.
1096 ;; Rescan between start of lines enclosing the region.
1102 "Fontify some lines the way `font-lock-fontify-buffer' would.
1103 The lines could be a function or paragraph, or a specified number of lines.
1104 If ARG is given, fontify that many lines before and after point, or 16 lines if
1105 no ARG is given and `font-lock-mark-block-function' is nil.
1106 If `font-lock-mark-block-function' non-nil and no ARG is given, it is used to
1107 delimit the region to fontify."
1110 deactivate-mark)
1111 ;; Make sure we have the right `font-lock-keywords' etc.
1129 ;;; End of Fontification functions.
1130 \f
1131 ;;; Additional text property functions.
1133 ;; The following text property functions should be builtins. This means they
1134 ;; should be written in C and put with all the other text property functions.
1135 ;; In the meantime, those that are used by font-lock.el are defined in Lisp
1136 ;; below and given a `font-lock-' prefix. Those that are not used are defined
1137 ;; in Lisp below and commented out. sm.
1140 "Prepend to one property of the text from START to END.
1141 Arguments PROP and VALUE specify the property and value to prepend to the value
1142 already in place. The resulting property values are always lists.
1143 Optional argument OBJECT is the string or buffer containing the text."
1150 object)
1154 "Append to one property of the text from START to END.
1155 Arguments PROP and VALUE specify the property and value to append to the value
1156 already in place. The resulting property values are always lists.
1157 Optional argument OBJECT is the string or buffer containing the text."
1164 object)
1168 "Fill in one property of the text from START to END.
1169 Arguments PROP and VALUE specify the property and value to put where none are
1170 already in place. Therefore existing property values are not overwritten.
1171 Optional argument OBJECT is the string or buffer containing the text."
1178 ;; For completeness: this is to `remove-text-properties' as `put-text-property'
1179 ;; is to `add-text-properties', etc.
1180 ;;(defun remove-text-property (start end property &optional object)
1181 ;; "Remove a property from text from START to END.
1182 ;;Argument PROPERTY is the property to remove.
1183 ;;Optional argument OBJECT is the string or buffer containing the text.
1184 ;;Return t if the property was actually removed, nil otherwise."
1185 ;; (remove-text-properties start end (list property) object))
1187 ;; For consistency: maybe this should be called `remove-single-property' like
1188 ;; `next-single-property-change' (not `next-single-text-property-change'), etc.
1189 ;;(defun remove-single-text-property (start end prop value &optional object)
1190 ;; "Remove a specific property value from text from START to END.
1191 ;;Arguments PROP and VALUE specify the property and value to remove. The
1192 ;;resulting property values are not equal to VALUE nor lists containing VALUE.
1193 ;;Optional argument OBJECT is the string or buffer containing the text."
1194 ;; (let ((start (text-property-not-all start end prop nil object)) next prev)
1195 ;; (while start
1196 ;; (setq next (next-single-property-change start prop object end)
1197 ;; prev (get-text-property start prop object))
1198 ;; (cond ((and (symbolp prev) (eq value prev))
1199 ;; (remove-text-property start next prop object))
1200 ;; ((and (listp prev) (memq value prev))
1201 ;; (let ((new (delq value prev)))
1202 ;; (cond ((null new)
1203 ;; (remove-text-property start next prop object))
1204 ;; ((= (length new) 1)
1205 ;; (put-text-property start next prop (car new) object))
1206 ;; (t
1207 ;; (put-text-property start next prop new object))))))
1208 ;; (setq start (text-property-not-all next end prop nil object)))))
1210 ;;; End of Additional text property functions.
1211 \f
1212 ;;; Syntactic regexp fontification functions.
1214 ;; These syntactic keyword pass functions are identical to those keyword pass
1215 ;; functions below, with the following exceptions; (a) they operate on
1216 ;; `font-lock-syntactic-keywords' of course, (b) they are all `defun' as speed
1217 ;; is less of an issue, (c) eval of property value does not occur JIT as speed
1218 ;; is less of an issue, (d) OVERRIDE cannot be `prepend' or `append' as it
1219 ;; makes no sense for `syntax-table' property values, (e) they do not do it
1220 ;; LOUDLY as it is not likely to be intensive.
1223 "Apply HIGHLIGHT following a match.
1224 HIGHLIGHT should be of the form MATCH-HIGHLIGHT,
1225 see `font-lock-syntactic-keywords'."
1231 ;; No match but we might not signal an error.
1237 ;; Flush the syntax-cache. I believe this is not necessary for
1238 ;; font-lock's use of syntax-ppss, but I'm not 100% sure and it can
1239 ;; still be necessary for other users of syntax-ppss anyway.
1243 ;; Cannot override existing fontification.
1247 ;; Override existing fontification.
1250 ;; Keep existing fontification.
1254 "Fontify according to KEYWORDS until LIMIT.
1255 KEYWORDS should be of the form MATCH-ANCHORED, see `font-lock-keywords',
1256 LIMIT can be modified by the value of its PRE-MATCH-FORM."
1258 ;; Evaluate PRE-MATCH-FORM.
1260 ;; Set LIMIT to value of PRE-MATCH-FORM or the end of line.
1265 ;; Find an occurrence of `matcher' before `limit'.
1269 ;; Apply each highlight to this instance of `matcher'.
1274 ;; Evaluate POST-MATCH-FORM.
1278 "Fontify according to `font-lock-syntactic-keywords' between START and END.
1279 START should be at the beginning of a line."
1280 ;; Ensure the beginning of the file is properly syntactic-fontified.
1285 ;; If `font-lock-syntactic-keywords' is a symbol, get the real keywords.
1288 font-lock-syntactic-keywords)))
1289 ;; If `font-lock-syntactic-keywords' is not compiled, compile it.
1292 font-lock-syntactic-keywords)))
1293 ;; Get down to business.
1296 keyword matcher highlights)
1298 ;; Find an occurrence of `matcher' from `start' to `end'.
1304 ;; Apply each highlight to this instance of `matcher', which may be
1305 ;; specific highlights or more keywords anchored to `matcher'.
1311 end))
1315 ;;; End of Syntactic regexp fontification functions.
1316 \f
1317 ;;; Syntactic fontification functions.
1326 "Put proper face on each string and comment between START and END.
1327 START should be at the beginning of a line."
1332 state face beg)
1335 ;;
1336 ;; Find the `start' state.
1338 ;;
1339 ;; Find each interesting place between here and `end'.
1350 comment-start-skip))
1351 ;; Find the comment delimiters
1352 ;; and use font-lock-comment-delimiter-face for them.
1356 comment-start-skip))
1358 font-lock-comment-delimiter-face)))
1361 font-lock-comment-delimiter-face))))
1366 ;;; End of Syntactic fontification functions.
1367 \f
1368 ;;; Keyword regexp fontification functions.
1371 "Apply HIGHLIGHT following a match.
1372 HIGHLIGHT should be of the form MATCH-HIGHLIGHT, see `font-lock-keywords'."
1377 ;; No match but we might not signal an error.
1386 ;; If `val' is nil, don't do anything. It is important to do it
1387 ;; explicitly, because when adding nil via things like
1388 ;; font-lock-append-text-property, the property is actually
1389 ;; changed from <face> to (<face>) which is undesirable. --Stef
1390 nil)
1392 ;; Cannot override existing fontification.
1396 ;; Override existing fontification.
1399 ;; Prepend to existing fontification.
1402 ;; Append to existing fontification.
1405 ;; Keep existing fontification.
1409 "Fontify according to KEYWORDS until LIMIT.
1410 KEYWORDS should be of the form MATCH-ANCHORED, see `font-lock-keywords',
1411 LIMIT can be modified by the value of its PRE-MATCH-FORM."
1414 ;; Evaluate PRE-MATCH-FORM.
1416 ;; Set LIMIT to value of PRE-MATCH-FORM or the end of line.
1421 ;; this is a multiline anchored match
1422 ;; (setq font-lock-multiline t)
1426 limit
1429 ;; Find an occurrence of `matcher' before `limit'.
1434 ;; Apply each highlight to this instance of `matcher'.
1439 ;; Evaluate POST-MATCH-FORM.
1443 "Fontify according to `font-lock-keywords' between START and END.
1444 START should be at the beginning of a line.
1445 LOUDLY, if non-nil, allows progress-meter bar."
1453 keyword matcher highlights)
1454 ;;
1455 ;; Fontify each item in `font-lock-keywords' from `start' to `end'.
1459 ;;
1460 ;; Find an occurrence of `matcher' from `start' to `end'.
1467 ;; Beware empty string matches since they will
1468 ;; loop indefinitely.
1475 ;; this is a multiline regexp match
1476 ;; (setq font-lock-multiline t)
1485 ;; Apply each highlight to this instance of `matcher', which may be
1486 ;; specific highlights or more keywords anchored to `matcher'.
1493 ;; Ensure forward progress. `pos' is a marker because anchored
1494 ;; keyword may add/delete text (this happens e.g. in grep.el).
1500 ;;; End of Keyword regexp fontification functions.
1501 \f
1502 ;; Various functions.
1505 "Compile KEYWORDS into the form (t KEYWORDS COMPILED...)
1506 Here each COMPILED is of the form (MATCHER HIGHLIGHT ...) as shown in the
1507 `font-lock-keywords' doc string.
1508 If REGEXP is non-nil, it means these keywords are used for
1509 `font-lock-keywords' rather than for `font-lock-syntactic-keywords'."
1511 ;; This should never happen. But some external packages sometimes
1512 ;; call font-lock in unexpected and incorrect ways. It's important to
1513 ;; stop processing at this point, otherwise we may end up changing the
1514 ;; global value of font-lock-keywords and break highlighting in many
1515 ;; other buffers.
1518 keywords
1524 font-lock-beginning-of-syntax-function)
1527 ;; Try to detect when a string or comment contains something that
1528 ;; looks like a defun and would thus confuse font-lock.
1536 font-lock-comment-face))
1539 prepend)))))
1540 keywords))
1548 ;; If FORM is a FACENAME then quote it. Otherwise ignore the quote.
1559 keyword)))
1562 "Evalulate KEYWORDS if a function (funcall) or variable (eval) name."
1564 keywords
1570 "Return value in ALIST for `major-mode', or ALIST if it is not an alist.
1571 Structure is ((MAJOR-MODE . VALUE) ...) where MAJOR-MODE may be t."
1574 alist))
1577 "Return LEVELth element of KEYWORDS.
1578 A LEVEL of nil is equal to a LEVEL of 0, a LEVEL of t is equal to
1579 \(1- (length KEYWORDS))."
1581 keywords)
1593 "Set fontification defaults appropriately for this mode.
1594 Sets various variables using `font-lock-defaults' (or, if nil, using
1595 `font-lock-defaults-alist') and `font-lock-maximum-decoration'."
1596 ;; Set fontification defaults iff not previously set for correct major mode.
1606 font-lock-defaults-alist)))))
1614 ;; Syntactic fontification?
1617 ;; Case fold during regexp fontification?
1620 ;; Syntax table for regexp and syntactic fontification?
1625 ;; The character to modify may be a single CHAR or a STRING.
1631 ;; Syntax function for syntactic fontification?
1635 ;; Variable alist?
1638 ;; Set up `font-lock-keywords' last because its value might depend
1639 ;; on other settings (e.g. font-lock-compile-keywords uses
1640 ;; font-lock-beginning-of-syntax-function).
1643 ;; Local fontification?
1649 ;; Now compile the keywords.
1653 \f
1654 ;;; Colour etc. support.
1656 ;; Note that `defface' will not overwrite any faces declared above via
1657 ;; `custom-declare-face'.
1672 )
1674 )
1676 "Font Lock mode face used to highlight comments."
1687 "Font Lock mode face used to highlight comment delimiters."
1699 "Font Lock mode face used to highlight strings."
1704 "Font Lock mode face used to highlight documentation."
1716 "Font Lock mode face used to highlight keywords."
1728 "Font Lock mode face used to highlight builtins."
1738 "Font Lock mode face used to highlight function names."
1752 "Font Lock mode face used to highlight variable names."
1764 "Font Lock mode face used to highlight type and classes."
1778 "Font Lock mode face used to highlight constants and labels."
1788 "Font Lock mode face used to highlight warnings."
1793 "Font Lock mode face used to highlight easy to overlook negation."
1798 "Font Lock mode face used to highlight preprocessor directives."
1803 "Font Lock mode face for backslashes in Lisp regexp grouping constructs."
1808 "Font Lock mode face used to highlight grouping constructs in Lisp regexps."
1811 ;;; End of Colour etc. support.
1812 \f
1813 ;;; Menu support.
1815 ;; This section of code is commented out because Emacs does not have real menu
1816 ;; buttons. (We can mimic them by putting "( ) " or "(X) " at the beginning of
1817 ;; the menu entry text, but with Xt it looks both ugly and embarrassingly
1818 ;; amateur.) If/When Emacs gets real menus buttons, put in menu-bar.el after
1819 ;; the entry for "Text Properties" something like:
1820 ;;
1821 ;; (define-key menu-bar-edit-menu [font-lock]
1822 ;; (cons "Syntax Highlighting" font-lock-menu))
1823 ;;
1824 ;; and remove a single ";" from the beginning of each line in the rest of this
1825 ;; section. Probably the mechanism for telling the menu code what are menu
1826 ;; buttons and when they are on or off needs tweaking. I have assumed that the
1827 ;; mechanism is via `menu-toggle' and `menu-selected' symbol properties. sm.
1829 ;;;;;###autoload
1830 ;;(progn
1831 ;; ;; Make the Font Lock menu.
1832 ;; (defvar font-lock-menu (make-sparse-keymap "Syntax Highlighting"))
1833 ;; ;; Add the menu items in reverse order.
1834 ;; (define-key font-lock-menu [fontify-less]
1835 ;; '("Less In Current Buffer" . font-lock-fontify-less))
1836 ;; (define-key font-lock-menu [fontify-more]
1837 ;; '("More In Current Buffer" . font-lock-fontify-more))
1838 ;; (define-key font-lock-menu [font-lock-sep]
1839 ;; '("--"))
1840 ;; (define-key font-lock-menu [font-lock-mode]
1841 ;; '("In Current Buffer" . font-lock-mode))
1842 ;; (define-key font-lock-menu [global-font-lock-mode]
1843 ;; '("In All Buffers" . global-font-lock-mode)))
1844 ;;
1845 ;;;;;###autoload
1846 ;;(progn
1847 ;; ;; We put the appropriate `menu-enable' etc. symbol property values on when
1848 ;; ;; font-lock.el is loaded, so we don't need to autoload the three variables.
1849 ;; (put 'global-font-lock-mode 'menu-toggle t)
1850 ;; (put 'font-lock-mode 'menu-toggle t)
1851 ;; (put 'font-lock-fontify-more 'menu-enable '(identity))
1852 ;; (put 'font-lock-fontify-less 'menu-enable '(identity)))
1853 ;;
1854 ;; ;; Put the appropriate symbol property values on now. See above.
1855 ;;(put 'global-font-lock-mode 'menu-selected 'global-font-lock-mode)
1856 ;;(put 'font-lock-mode 'menu-selected 'font-lock-mode)
1857 ;;(put 'font-lock-fontify-more 'menu-enable '(nth 2 font-lock-fontify-level))
1858 ;;(put 'font-lock-fontify-less 'menu-enable '(nth 1 font-lock-fontify-level))
1859 ;;
1860 ;;(defvar font-lock-fontify-level nil) ; For less/more fontification.
1861 ;;
1862 ;;(defun font-lock-fontify-level (level)
1863 ;; (let ((font-lock-maximum-decoration level))
1864 ;; (when font-lock-mode
1865 ;; (font-lock-mode))
1866 ;; (font-lock-mode)
1867 ;; (when font-lock-verbose
1868 ;; (message "Fontifying %s... level %d" (buffer-name) level))))
1869 ;;
1870 ;;(defun font-lock-fontify-less ()
1871 ;; "Fontify the current buffer with less decoration.
1872 ;;See `font-lock-maximum-decoration'."
1873 ;; (interactive)
1874 ;; ;; Check in case we get called interactively.
1875 ;; (if (nth 1 font-lock-fontify-level)
1876 ;; (font-lock-fontify-level (1- (car font-lock-fontify-level)))
1877 ;; (error "No less decoration")))
1878 ;;
1879 ;;(defun font-lock-fontify-more ()
1880 ;; "Fontify the current buffer with more decoration.
1881 ;;See `font-lock-maximum-decoration'."
1882 ;; (interactive)
1883 ;; ;; Check in case we get called interactively.
1884 ;; (if (nth 2 font-lock-fontify-level)
1885 ;; (font-lock-fontify-level (1+ (car font-lock-fontify-level)))
1886 ;; (error "No more decoration")))
1887 ;;
1888 ;; ;; This should be called by `font-lock-set-defaults'.
1889 ;;(defun font-lock-set-menu ()
1890 ;; ;; Activate less/more fontification entries if there are multiple levels for
1891 ;; ;; the current buffer. Sets `font-lock-fontify-level' to be of the form
1892 ;; ;; (CURRENT-LEVEL IS-LOWER-LEVEL-P IS-HIGHER-LEVEL-P) for menu activation.
1893 ;; (let ((keywords (or (nth 0 font-lock-defaults)
1894 ;; (nth 1 (assq major-mode font-lock-defaults-alist))))
1895 ;; (level (font-lock-value-in-major-mode font-lock-maximum-decoration)))
1896 ;; (make-local-variable 'font-lock-fontify-level)
1897 ;; (if (or (symbolp keywords) (= (length keywords) 1))
1898 ;; (font-lock-unset-menu)
1899 ;; (cond ((eq level t)
1900 ;; (setq level (1- (length keywords))))
1901 ;; ((or (null level) (zerop level))
1902 ;; ;; The default level is usually, but not necessarily, level 1.
1903 ;; (setq level (- (length keywords)
1904 ;; (length (member (eval (car keywords))
1905 ;; (mapcar 'eval (cdr keywords))))))))
1906 ;; (setq font-lock-fontify-level (list level (> level 1)
1907 ;; (< level (1- (length keywords))))))))
1908 ;;
1909 ;; ;; This should be called by `font-lock-unset-defaults'.
1910 ;;(defun font-lock-unset-menu ()
1911 ;; ;; Deactivate less/more fontification entries.
1912 ;; (setq font-lock-fontify-level nil))
1914 ;;; End of Menu support.
1915 \f
1916 ;;; Various regexp information shared by several modes.
1917 ;; ;; Information specific to a single mode should go in its load library.
1919 ;; Font Lock support for C, C++, Objective-C and Java modes is now in
1920 ;; cc-fonts.el (and required by cc-mode.el). However, the below function
1921 ;; should stay in font-lock.el, since it is used by other libraries. sm.
1924 "Match, and move over, any declaration/definition item after point.
1925 Matches after point, but ignores leading whitespace and `*' characters.
1926 Does not move further than LIMIT.
1928 The expected syntax of a declaration/definition item is `word' (preceded by
1929 optional whitespace and `*' characters and proceeded by optional whitespace)
1930 optionally followed by a `('. Everything following the item (but belonging to
1931 it) is expected to be skip-able by `scan-sexps', and items are expected to be
1932 separated with a `,' and to be terminated with a `;'.
1934 Thus the regexp matches after point: word (
1935 ^^^^ ^
1936 Where the match subexpressions are: 1 2
1938 The item is delimited by (match-beginning 1) and (match-end 1).
1939 If (match-beginning 2) is non-nil, the item is followed by a `('.
1941 This function could be MATCHER in a MATCH-ANCHORED `font-lock-keywords' item."
1944 ;; If `word' is followed by a double open-paren, it's probably
1945 ;; a macro used for "int myfun P_ ((int arg1))". Let's go back one
1946 ;; word to try and match `myfun' rather than `P_'.
1951 ;; Looks like it was something else, so go back to where we
1952 ;; were and reset the match data by rematching.
1958 ;; Restrict to the LIMIT.
1961 ;; Move over any item value, etc., to the next item.
1966 \f
1967 ;; Lisp.
1973 ;; Function declarations.
1980 ;; Variable declarations.
1982 ;; Structure declarations.
1985 ;; Any whitespace and defined object.
1992 nil t))
1993 ;; Emacs Lisp autoload cookies.
1995 ;; Regexp negated char group.
2013 "with-category-table"
2022 ;; Control structures. Common Lisp forms.
2043 ;; Exit/Feature symbols as constants.
2048 ;; Erroneous structures.
2049 ("(\\(abort\\|assert\\|warn\\|check-type\\|cerror\\|error\\|signal\\)\\>" 1 font-lock-warning-face)
2050 ;; Words inside \\[] tend to be for `substitute-command-keys'.
2052 ;; Words inside `' tend to be symbol names.
2054 ;; Constant values.
2056 ;; ELisp and CLisp `&' keywords as types.
2058 ;; ELisp regexp grouping constructs
2061 ;; The following loop is needed to continue searching after matches
2062 ;; that do not occur in strings. The associated regexp matches one
2063 ;; of `\\\\' `\\(' `\\(?:' `\\|' `\\)'. `\\\\' has been included to
2064 ;; avoid highlighting, for example, `\\(' in `\\\\('.
2065 (while (re-search-forward "\\(\\\\\\\\\\)\\(?:\\(\\\\\\\\\\)\\|\\((\\(?:\\?:\\)?\\|[|)]\\)\\)" bound t)
2074 ;;; This is too general -- rms.
2075 ;;; A user complained that he has functions whose names start with `do'
2076 ;;; and that they get the wrong color.
2077 ;;; ;; CL `with-' and `do-' constructs
2078 ;;; ("(\\(\\(do-\\|with-\\)\\(\\s_\\|\\w\\)*\\)" 1 font-lock-keyword-face)
2079 )))
2084 \f
2087 ;; arch-tag: 682327e4-64d8-4057-b20b-1fbb9f1fc54c
2088 ;;; font-lock.el ends here