| blob | 85a7ff1b371ec88f02fa43e4f79e479f3f6d2904 |
1 ;;; font-lock.el --- Electric font lock mode
3 ;; Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
4 ;; 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010
5 ;; Free Software Foundation, Inc.
7 ;; Author: Jamie Zawinski
8 ;; Richard Stallman
9 ;; Stefan Monnier
10 ;; Maintainer: FSF
11 ;; Keywords: languages, faces
13 ;; This file is part of GNU Emacs.
15 ;; GNU Emacs is free software: you can redistribute it and/or modify
16 ;; it under the terms of the GNU General Public License as published by
17 ;; the Free Software Foundation, either version 3 of the License, or
18 ;; (at your option) any later version.
20 ;; GNU Emacs is distributed in the hope that it will be useful,
21 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
22 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
23 ;; GNU General Public License for more details.
25 ;; You should have received a copy of the GNU General Public License
26 ;; along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.
28 ;;; Commentary:
30 ;; Font Lock mode is a minor mode that causes your comments to be displayed in
31 ;; one face, strings in another, reserved words in another, and so on.
32 ;;
33 ;; Comments will be displayed in `font-lock-comment-face'.
34 ;; Strings will be displayed in `font-lock-string-face'.
35 ;; Regexps are used to display selected patterns in other faces.
36 ;;
37 ;; To make the text you type be fontified, use M-x font-lock-mode RET.
38 ;; When this minor mode is on, the faces of the current line are updated with
39 ;; every insertion or deletion.
40 ;;
41 ;; To turn Font Lock mode on automatically, add this to your ~/.emacs file:
42 ;;
43 ;; (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
44 ;;
45 ;; Or if you want to turn Font Lock mode on in many modes:
46 ;;
47 ;; (global-font-lock-mode t)
48 ;;
49 ;; Fontification for a particular mode may be available in a number of levels
50 ;; of decoration. The higher the level, the more decoration, but the more time
51 ;; it takes to fontify. See the variable `font-lock-maximum-decoration', and
52 ;; also the variable `font-lock-maximum-size'. Support modes for Font Lock
53 ;; mode can be used to speed up Font Lock mode. See `font-lock-support-mode'.
54 \f
55 ;;; How Font Lock mode fontifies:
57 ;; When Font Lock mode is turned on in a buffer, it (a) fontifies the entire
58 ;; buffer and (b) installs one of its fontification functions on one of the
59 ;; hook variables that are run by Emacs after every buffer change (i.e., an
60 ;; insertion or deletion). Fontification means the replacement of `face' text
61 ;; properties in a given region; Emacs displays text with these `face' text
62 ;; properties appropriately.
63 ;;
64 ;; Fontification normally involves syntactic (i.e., strings and comments) and
65 ;; regexp (i.e., keywords and everything else) passes. There are actually
66 ;; three passes; (a) the syntactic keyword pass, (b) the syntactic pass and (c)
67 ;; the keyword pass. Confused?
68 ;;
69 ;; The syntactic keyword pass places `syntax-table' text properties in the
70 ;; buffer according to the variable `font-lock-syntactic-keywords'. It is
71 ;; necessary because Emacs' syntax table is not powerful enough to describe all
72 ;; the different syntactic constructs required by the sort of people who decide
73 ;; that a single quote can be syntactic or not depending on the time of day.
74 ;; (What sort of person could decide to overload the meaning of a quote?)
75 ;; Obviously the syntactic keyword pass must occur before the syntactic pass.
76 ;;
77 ;; The syntactic pass places `face' text properties in the buffer according to
78 ;; syntactic context, i.e., according to the buffer's syntax table and buffer
79 ;; text's `syntax-table' text properties. It involves using a syntax parsing
80 ;; function to determine the context of different parts of a region of text. A
81 ;; syntax parsing function is necessary because generally strings and/or
82 ;; comments can span lines, and so the context of a given region is not
83 ;; necessarily apparent from the content of that region. Because the keyword
84 ;; pass only works within a given region, it is not generally appropriate for
85 ;; syntactic fontification. This is the first fontification pass that makes
86 ;; changes visible to the user; it fontifies strings and comments.
87 ;;
88 ;; The keyword pass places `face' text properties in the buffer according to
89 ;; the variable `font-lock-keywords'. It involves searching for given regexps
90 ;; (or calling given search functions) within the given region. This is the
91 ;; second fontification pass that makes changes visible to the user; it
92 ;; fontifies language reserved words, etc.
93 ;;
94 ;; Oh, and the answer is, "Yes, obviously just about everything should be done
95 ;; in a single syntactic pass, but the only syntactic parser available
96 ;; understands only strings and comments." Perhaps one day someone will write
97 ;; some syntactic parsers for common languages and a son-of-font-lock.el could
98 ;; use them rather then relying so heavily on the keyword (regexp) pass.
100 ;;; How Font Lock mode supports modes or is supported by modes:
102 ;; Modes that support Font Lock mode do so by defining one or more variables
103 ;; whose values specify the fontification. Font Lock mode knows of these
104 ;; variable names from (a) the buffer local variable `font-lock-defaults', if
105 ;; non-nil, or (b) the global variable `font-lock-defaults-alist', if the major
106 ;; mode has an entry. (Font Lock mode is set up via (a) where a mode's
107 ;; patterns are distributed with the mode's package library, and (b) where a
108 ;; mode's patterns are distributed with font-lock.el itself. An example of (a)
109 ;; is Pascal mode, an example of (b) is Lisp mode. Normally, the mechanism is
110 ;; (a); (b) is used where it is not clear which package library should contain
111 ;; the pattern definitions.) Font Lock mode chooses which variable to use for
112 ;; fontification based on `font-lock-maximum-decoration'.
113 ;;
114 ;; Font Lock mode fontification behavior can be modified in a number of ways.
115 ;; See the below comments and the comments distributed throughout this file.
117 ;;; Constructing patterns:
119 ;; See the documentation for the variable `font-lock-keywords'.
120 ;;
121 ;; Efficient regexps for use as MATCHERs for `font-lock-keywords' and
122 ;; `font-lock-syntactic-keywords' can be generated via the function
123 ;; `regexp-opt'.
125 ;;; Adding patterns for modes that already support Font Lock:
127 ;; Though Font Lock highlighting patterns already exist for many modes, it's
128 ;; likely there's something that you want fontified that currently isn't, even
129 ;; at the maximum fontification level. You can add highlighting patterns via
130 ;; `font-lock-add-keywords'. For example, say in some C
131 ;; header file you #define the token `and' to expand to `&&', etc., to make
132 ;; your C code almost readable. In your ~/.emacs there could be:
133 ;;
134 ;; (font-lock-add-keywords 'c-mode '("\\<\\(and\\|or\\|not\\)\\>"))
135 ;;
136 ;; Some modes provide specific ways to modify patterns based on the values of
137 ;; other variables. For example, additional C types can be specified via the
138 ;; variable `c-font-lock-extra-types'.
140 ;;; Adding patterns for modes that do not support Font Lock:
142 ;; Not all modes support Font Lock mode. If you (as a user of the mode) add
143 ;; patterns for a new mode, you must define in your ~/.emacs a variable or
144 ;; variables that specify regexp fontification. Then, you should indicate to
145 ;; Font Lock mode, via the mode hook setting `font-lock-defaults', exactly what
146 ;; support is required. For example, say Foo mode should have the following
147 ;; regexps fontified case-sensitively, and comments and strings should not be
148 ;; fontified automagically. In your ~/.emacs there could be:
149 ;;
150 ;; (defvar foo-font-lock-keywords
151 ;; '(("\\<\\(one\\|two\\|three\\)\\>" . font-lock-keyword-face)
152 ;; ("\\<\\(four\\|five\\|six\\)\\>" . font-lock-type-face))
153 ;; "Default expressions to highlight in Foo mode.")
154 ;;
155 ;; (add-hook 'foo-mode-hook
156 ;; (lambda ()
157 ;; (set (make-local-variable 'font-lock-defaults)
158 ;; '(foo-font-lock-keywords t))))
160 ;;; Adding Font Lock support for modes:
162 ;; Of course, it would be better that the mode already supports Font Lock mode.
163 ;; The package author would do something similar to above. The mode must
164 ;; define at the top-level a variable or variables that specify regexp
165 ;; fontification. Then, the mode command should indicate to Font Lock mode,
166 ;; via `font-lock-defaults', exactly what support is required. For example,
167 ;; say Bar mode should have the following regexps fontified case-insensitively,
168 ;; and comments and strings should be fontified automagically. In bar.el there
169 ;; could be:
170 ;;
171 ;; (defvar bar-font-lock-keywords
172 ;; '(("\\<\\(uno\\|due\\|tre\\)\\>" . font-lock-keyword-face)
173 ;; ("\\<\\(quattro\\|cinque\\|sei\\)\\>" . font-lock-type-face))
174 ;; "Default expressions to highlight in Bar mode.")
175 ;;
176 ;; and within `bar-mode' there could be:
177 ;;
178 ;; (set (make-local-variable 'font-lock-defaults)
179 ;; '(bar-font-lock-keywords nil t))
180 \f
181 ;; What is fontification for? You might say, "It's to make my code look nice."
182 ;; I think it should be for adding information in the form of cues. These cues
183 ;; should provide you with enough information to both (a) distinguish between
184 ;; different items, and (b) identify the item meanings, without having to read
185 ;; the items and think about it. Therefore, fontification allows you to think
186 ;; less about, say, the structure of code, and more about, say, why the code
187 ;; doesn't work. Or maybe it allows you to think less and drift off to sleep.
188 ;;
189 ;; So, here are my opinions/advice/guidelines:
190 ;;
191 ;; - Highlight conceptual objects, such as function and variable names, and
192 ;; different objects types differently, i.e., (a) and (b) above, highlight
193 ;; function names differently to variable names.
194 ;; - Keep the faces distinct from each other as far as possible.
195 ;; i.e., (a) above.
196 ;; - Use the same face for the same conceptual object, across all modes.
197 ;; i.e., (b) above, all modes that have items that can be thought of as, say,
198 ;; keywords, should be highlighted with the same face, etc.
199 ;; - Make the face attributes fit the concept as far as possible.
200 ;; i.e., function names might be a bold color such as blue, comments might
201 ;; be a bright color such as red, character strings might be brown, because,
202 ;; err, strings are brown (that was not the reason, please believe me).
203 ;; - Don't use a non-nil OVERRIDE unless you have a good reason.
204 ;; Only use OVERRIDE for special things that are easy to define, such as the
205 ;; way `...' quotes are treated in strings and comments in Emacs Lisp mode.
206 ;; Don't use it to, say, highlight keywords in commented out code or strings.
207 ;; - Err, that's it.
208 \f
209 ;;; Code:
213 ;; Define core `font-lock' group.
215 "Font Lock mode text highlighting package."
221 "Faces for highlighting text."
226 "Extra mode-specific type names for highlighting declarations."
228 \f
229 ;; User variables.
232 "Maximum size of a buffer for buffer fontification.
233 Only buffers less than this can be fontified when Font Lock mode is turned on.
234 If nil, means size is irrelevant.
235 If a list, each element should be a cons pair of the form (MAJOR-MODE . SIZE),
236 where MAJOR-MODE is a symbol or t (meaning the default). For example:
237 ((c-mode . 256000) (c++-mode . 256000) (rmail-mode . 1048576))
238 means that the maximum size is 250K for buffers in C or C++ modes, one megabyte
239 for buffers in Rmail mode, and size is irrelevant otherwise."
254 "Maximum decoration level for fontification.
255 If nil, use the default decoration (typically the minimum available).
256 If t, use the maximum decoration available.
257 If a number, use that level of decoration (or if not available the maximum).
258 If a list, each element should be a cons pair of the form (MAJOR-MODE . LEVEL),
259 where MAJOR-MODE is a symbol or t (meaning the default). For example:
260 ((c-mode . t) (c++-mode . 2) (t . 1))
261 means use the maximum decoration available for buffers in C mode, level 2
262 decoration for buffers in C++ mode, and level 1 decoration otherwise."
279 "If non-nil, means show status messages for buffer fontification.
280 If a number, only buffers greater than this size have fontification messages."
285 \f
287 ;; Originally these variable values were face names such as `bold' etc.
288 ;; Now we create our own faces, but we keep these variables for compatibility
289 ;; and they give users another mechanism for changing face appearance.
290 ;; We now allow a FACENAME in `font-lock-keywords' to be any expression that
291 ;; returns a face. So the easiest thing is to continue using these variables,
292 ;; rather than sometimes evaling FACENAME and sometimes not. sm.
294 ;; Note that in new code, in the vast majority of cases there is no
295 ;; need to create variables that specify face names. Simply using
296 ;; faces directly is enough. Font-lock is not a template to be
297 ;; followed in this area.
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 if
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
480 "Alist of `font-lock-keywords' elements to be removed for major modes.
482 Each element has the form (MODE . KEYWORDS). `font-lock-set-defaults'
483 removes the elements in the list KEYWORDS from `font-lock-keywords'
484 when Font Lock is turned on in major mode MODE.
486 This is normally set via `font-lock-add-keywords' and
490 "*Non-nil means Font Lock should not fontify comments or strings.
494 "*Non-nil means the patterns in `font-lock-keywords' are case-insensitive.
495 This is set via the function `font-lock-set-defaults', based on
500 "Point up to which `font-lock-syntactic-keywords' has been applied.
501 If nil, this is ignored, in which case the syntactic fontification may
508 "Function to determine which face to use when fontifying syntactically.
509 The function is called with a single parameter (the state as returned by
510 `parse-partial-sexp' at the beginning of the region to highlight) and
514 "A list of the syntactic keywords to put syntax properties on.
515 The value can be the list itself, or the name of a function or variable
516 whose value is the list.
518 See `font-lock-keywords' for a description of the form of this list;
519 only the differences are stated here. MATCH-HIGHLIGHT should be of the form:
521 (SUBEXP SYNTAX OVERRIDE LAXMATCH)
523 where SYNTAX can be a string (as taken by `modify-syntax-entry'), a syntax
524 table, a cons cell (as returned by `string-to-syntax') or an expression whose
525 value is such a form. OVERRIDE cannot be `prepend' or `append'.
527 Here are two examples of elements of `font-lock-syntactic-keywords'
528 and what they do:
533 dollar-sign character. Hash characters in other contexts will still
534 follow whatever the syntax table says about the hash character.
540 gives a pair single-quotes, which surround a single character, a SYNTAX of
542 contexts will not be affected.
547 "Non-nil means use this syntax table for fontifying.
548 If this is nil, the major mode's syntax table is used.
552 "*Non-nil means use this function to move back outside all constructs.
553 When called with no args it should move point backward to a place which
554 is not in a string or comment and not within any bracket-pairs (or else,
555 a place such that any bracket-pairs outside it can be ignored for Emacs
556 syntax analysis and fontification).
558 If this is nil, Font Lock uses `syntax-begin-function' to move back
559 outside of any comment, string, or sexp. This variable is semi-obsolete;
560 we recommend setting `syntax-begin-function' instead.
567 "*Non-nil means use this function to mark a block of text.
568 When called with no args it should leave point at the beginning of any
569 enclosing textual block and mark at the end.
573 "Function to use for fontifying the buffer.
577 "Function to use for unfontifying the buffer.
578 This is used when turning off Font Lock mode.
582 "Function to use for fontifying a region.
583 It should take two args, the beginning and end of the region, and an optional
584 third arg VERBOSE. If VERBOSE is non-nil, the function should print status
588 "Function to use for unfontifying a region.
589 It should take two args, the beginning and end of the region.
593 "List of Font Lock mode related modes that should not be turned on.
594 Currently, valid mode names are `fast-lock-mode', `jit-lock-mode' and
598 "Whether font-lock should cater to multiline keywords.
599 If nil, don't try to handle multiline patterns.
600 If t, always handle multiline patterns.
601 If `undecided', don't try to handle multiline patterns until you see one.
605 \f
606 ;; Font Lock mode.
609 ;;
610 ;; We don't do this at the top-level as we only use non-autoloaded macros.
612 ;;
613 ;; Borrowed from lazy-lock.el.
614 ;; We use this to preserve or protect things when modifying text properties.
616 "Bind variables according to VARLIST and eval BODY restoring buffer state."
625 deactivate-mark
626 buffer-file-name
627 buffer-file-truename))
633 ;;
634 ;; Shut up the byte compiler.
638 ;; Turn on Font Lock mode.
643 ;; Fontify the buffer if we have to.
646 nil)
652 ;; Turn off Font Lock mode.
659 "Add highlighting KEYWORDS for MODE.
661 MODE should be a symbol, the major mode command name, such as `c-mode'
662 or nil. If nil, highlighting keywords are added for the current buffer.
663 KEYWORDS should be a list; see the variable `font-lock-keywords'.
664 By default they are added at the beginning of the current highlighting list.
665 If optional argument HOW is `set', they are used to replace the current
666 highlighting list. If HOW is any other non-nil value, they are added at the
667 end of the current highlighting list.
669 For example:
671 (font-lock-add-keywords 'c-mode
675 adds two fontification patterns for C mode, to fontify `FIXME:' words, even in
676 comments, and to fontify `and', `or' and `not' words as keywords.
678 The above procedure will only add the keywords for C mode, not
679 for modes derived from C mode. To add them for derived modes too,
680 pass nil for MODE and add the call to c-mode-hook.
682 For example:
684 (add-hook 'c-mode-hook
685 (lambda ()
686 (font-lock-add-keywords nil
689 font-lock-keyword-face)))))
691 The above procedure may fail to add keywords to derived modes if
692 some involved major mode does not follow the standard conventions.
693 File a bug report if this happens, so the major mode can be corrected.
695 Note that some modes have specialized support for additional patterns, e.g.,
696 see the variables `c-font-lock-extra-types', `c++-font-lock-extra-types',
697 `objc-font-lock-extra-types' and `java-font-lock-extra-types'."
699 ;; If MODE is non-nil, add the KEYWORDS and HOW spec to
700 ;; `font-lock-keywords-alist' so `font-lock-set-defaults' uses them.
707 ;; Make sure that `font-lock-removed-keywords-alist' does not
708 ;; contain the new keywords.
713 ;; The major mode has not set any keywords, so when we enabled
714 ;; font-lock-mode it only enabled the font-core.el part, not the
715 ;; font-lock-mode-internal. Try again.
719 ;; Otherwise set or add the keywords now.
720 ;; This is a no-op if it has been done already in this buffer
721 ;; for the correct major mode.
724 ;; Bring back the user-level (uncompiled) keywords.
727 ;; Now modify or replace them.
733 font-lock-keywords)))
737 ;; If the keywords were compiled before, compile them again.
743 "Update `font-lock-removed-keywords-alist' when adding new KEYWORDS to MODE."
744 ;; When font-lock is enabled first all keywords in the list
745 ;; `font-lock-keywords-alist' are added, then all keywords in the
746 ;; list `font-lock-removed-keywords-alist' are removed. If a
747 ;; keyword was once added, removed, and then added again it must be
748 ;; removed from the removed-keywords list. Otherwise the second add
749 ;; will not take effect.
753 ;; A new set of keywords is defined. Forget all about
754 ;; our old keywords that should be removed.
757 ;; Delete all previously removed keywords.
760 ;; Delete the mode cell if empty.
765 ;; Written by Anders Lindgren <andersl@andersl.com>.
766 ;;
767 ;; Case study:
768 ;; (I) The keywords are removed from a major mode.
769 ;; In this case the keyword could be local (i.e. added earlier by
770 ;; `font-lock-add-keywords'), global, or both.
771 ;;
772 ;; (a) In the local case we remove the keywords from the variable
773 ;; `font-lock-keywords-alist'.
774 ;;
775 ;; (b) The actual global keywords are not known at this time.
776 ;; All keywords are added to `font-lock-removed-keywords-alist',
777 ;; when font-lock is enabled those keywords are removed.
778 ;;
779 ;; Note that added keywords are taken out of the list of removed
780 ;; keywords. This ensure correct operation when the same keyword
781 ;; is added and removed several times.
782 ;;
783 ;; (II) The keywords are removed from the current buffer.
785 "Remove highlighting KEYWORDS for MODE.
787 MODE should be a symbol, the major mode command name, such as `c-mode'
788 or nil. If nil, highlighting keywords are removed for the current buffer.
790 To make the removal apply to modes derived from MODE as well,
791 pass nil for MODE and add the call to MODE-hook. This may fail
792 for some derived modes if some involved major mode does not
793 follow the standard conventions. File a bug report if this
794 happens, so the major mode can be corrected."
796 ;; Remove one keyword at the time.
799 ;; If MODE is non-nil, remove the KEYWORD from
800 ;; `font-lock-keywords-alist'.
803 ;; `keywords-list-how-pair' is a cons with a list of
804 ;; keywords in the car top-cell and the original how
805 ;; argument in the cdr top-cell.
808 ;; Remove keyword list/how pair when the keyword list
809 ;; is empty and how doesn't specify `set'. (If it
810 ;; should be deleted then previously deleted keywords
811 ;; would appear again.)
818 ;; Final cleanup, remove major mode cell if last keyword
819 ;; was deleted.
823 ;; Remember the keyword in case it is not local.
829 font-lock-removed-keywords-alist))))))
831 ;; Otherwise remove it immediately.
834 ;; Bring back the user-level (uncompiled) keywords.
838 ;; Edit them.
844 ;; If the keywords were compiled before, compile them again.
848 \f
849 ;;; Font Lock Support mode.
851 ;; This is the code used to interface font-lock.el with any of its add-on
852 ;; packages, and provide the user interface. Packages that have their own
853 ;; local buffer fontification functions (see below) may have to call
854 ;; `font-lock-after-fontify-buffer' and/or `font-lock-after-unfontify-buffer'
855 ;; themselves.
858 "Support mode for Font Lock mode.
859 Support modes speed up Font Lock mode by being choosy about when fontification
860 occurs. The default support mode, Just-in-time Lock mode (symbol
861 `jit-lock-mode'), is recommended.
863 Other, older support modes are Fast Lock mode (symbol `fast-lock-mode') and
864 Lazy Lock mode (symbol `lazy-lock-mode'). See those modes for more info.
865 However, they are no longer recommended, as Just-in-time Lock mode is better.
867 If nil, means support for Font Lock mode is never performed.
868 If a symbol, use that support mode.
869 If a list, each element should be of the form (MAJOR-MODE . SUPPORT-MODE),
870 where MAJOR-MODE is a symbol or t (meaning the default). For example:
871 ((c-mode . fast-lock-mode) (c++-mode . fast-lock-mode) (t . lazy-lock-mode))
872 means that Fast Lock mode is used to support Font Lock mode for buffers in C or
873 C++ modes, and Lazy Lock mode is used to support Font Lock mode otherwise.
875 The value of this variable is used when Font Lock mode is turned on."
891 ))
913 ;; Prepare for jit-lock
918 ;; Don't fontify eagerly (and don't abort if the buffer is large).
920 ;; Use jit-lock.
923 ;; Tell jit-lock how we extend the region to refontify.
925 'font-lock-extend-jit-lock-region-after-change
926 nil t)))))
933 ;; Reset local vars to the non-jit-lock case.
941 ;; Useless now that jit-lock intercepts font-lock-fontify-buffer. -sm
942 ;; (jit-lock-mode
943 ;; (jit-lock-after-fontify-buffer))
950 ;; Useless as well. It's only called when:
951 ;; - turning off font-lock: it does not matter if we leave spurious
952 ;; `fontified' text props around since jit-lock-mode is also off.
953 ;; - font-lock-default-fontify-buffer fails: this is not run
954 ;; any more anyway. -sm
955 ;;
956 ;; (jit-lock-mode
957 ;; (jit-lock-after-unfontify-buffer))
961 ;;; End of Font Lock Support mode.
962 \f
963 ;;; Fontification functions.
965 ;; Rather than the function, e.g., `font-lock-fontify-region' containing the
966 ;; code to fontify a region, the function runs the function whose name is the
967 ;; value of the variable, e.g., `font-lock-fontify-region-function'. Normally,
968 ;; the value of this variable is, e.g., `font-lock-default-fontify-region'
969 ;; which does contain the code to fontify a region. However, the value of the
970 ;; variable could be anything and thus, e.g., `font-lock-fontify-region' could
971 ;; do anything. The indirection of the fontification functions gives major
972 ;; modes the capability of modifying the way font-lock.el fontifies. Major
973 ;; modes can modify the values of, e.g., `font-lock-fontify-region-function',
974 ;; via the variable `font-lock-defaults'.
975 ;;
976 ;; For example, Rmail mode sets the variable `font-lock-defaults' so that
977 ;; font-lock.el uses its own function for buffer fontification. This function
978 ;; makes fontification be on a message-by-message basis and so visiting an
979 ;; RMAIL file is much faster. A clever implementation of the function might
980 ;; fontify the headers differently than the message body. (It should, and
981 ;; correspondingly for Mail mode, but I can't be bothered to do the work. Can
982 ;; you?) This hints at a more interesting use...
983 ;;
984 ;; Languages that contain text normally contained in different major modes
985 ;; could define their own fontification functions that treat text differently
986 ;; depending on its context. For example, Perl mode could arrange that here
987 ;; docs are fontified differently than Perl code. Or Yacc mode could fontify
988 ;; rules one way and C code another. Neat!
989 ;;
990 ;; A further reason to use the fontification indirection feature is when the
991 ;; default syntactual fontification, or the default fontification in general,
992 ;; is not flexible enough for a particular major mode. For example, perhaps
993 ;; comments are just too hairy for `font-lock-fontify-syntactically-region' to
994 ;; cope with. You need to write your own version of that function, e.g.,
995 ;; `hairy-fontify-syntactically-region', and make your own version of
996 ;; `hairy-fontify-region' call that function before calling
997 ;; `font-lock-fontify-keywords-region' for the normal regexp fontification
998 ;; pass. And Hairy mode would set `font-lock-defaults' so that font-lock.el
999 ;; would call your region fontification function instead of its own. For
1000 ;; example, TeX modes could fontify {\foo ...} and \bar{...} etc. multi-line
1001 ;; directives correctly and cleanly. (It is the same problem as fontifying
1002 ;; multi-line strings and comments; regexps are not appropriate for the job.)
1005 "A function that determines the region to refontify after a change.
1007 This variable is either nil, or is a function that determines the
1008 region to refontify after a change.
1009 It is usually set by the major mode via `font-lock-defaults'.
1010 Font-lock calls this function after each buffer change.
1012 The function is given three parameters, the standard BEG, END, and OLD-LEN
1013 from `after-change-functions'. It should return either a cons of the beginning
1014 and end buffer positions \(in that order) of the region to refontify, or nil
1015 \(which directs the caller to fontify a default region).
1016 This function should preserve the match-data.
1021 "Fontify the current buffer the way the function `font-lock-mode' would."
1042 font-lock-verbose)))
1046 ;; Make sure we fontify etc. in the whole buffer.
1055 ;; We don't restore the old fontification, so it's best to unfontify.
1059 ;; Make sure we unfontify etc. in the whole buffer.
1067 "If non-nil, font-lock will work on the non-widened buffer.
1068 Useful for things like RMAIL and Info where the whole buffer is not
1075 ;; This use of font-lock-multiline property is unreliable but is just
1076 ;; a handy heuristic: in case you don't have a function that does
1077 ;; /identification/ of multiline elements, you may still occasionally
1078 ;; discover them by accident (or you may /identify/ them but not in all
1079 ;; cases), in which case the font-lock-multiline property can help make
1080 ;; sure you will properly *re*identify them during refontification.
1081 font-lock-extend-region-multiline)
1082 "Special hook run just before proceeding to fontify a region.
1083 This is used to allow major modes to help font-lock find safe buffer positions
1084 as beginning and end of the fontified region. Its most common use is to solve
1085 the problem of /identification/ of multiline elements by providing a function
1086 that tries to find such elements and move the boundaries such that they do
1087 not fall in the middle of one.
1088 Each function is called with no argument; it is expected to adjust the
1089 dynamically bound variables `font-lock-beg' and `font-lock-end'; and return
1090 non-nil if it did make such an adjustment.
1091 These functions are run in turn repeatedly until they all return nil.
1093 ;; Mark it as a special hook which doesn't use any global setting
1094 ;; (i.e. doesn't obey the element t in the buffer-local value).
1098 "Move fontification boundaries away from any `font-lock-multiline' property."
1106 ;;
1112 changed))
1115 "Move fontification boundaries to beginning of lines."
1125 changed))
1135 ;; Use the fontification syntax table, if any.
1138 ;; Extend the region to fontify so that it starts and ends at
1139 ;; safe places.
1147 ;; If there's been a change, we should go through
1148 ;; the list again since this new position may
1149 ;; warrant a different answer from one of the fun
1150 ;; we've already seen.
1151 font-lock-extend-region-functions)))
1153 ;; Now do the fontification.
1160 ;; Clean up.
1163 ;; The following must be rethought, since keywords can override fontification.
1164 ;; ;; Now scan for keywords, but not if we are inside a comment now.
1165 ;; (or (and (not font-lock-keywords-only)
1166 ;; (let ((state (parse-partial-sexp beg end nil nil
1167 ;; font-lock-cache-state)))
1168 ;; (or (nth 4 state) (nth 7 state))))
1169 ;; (font-lock-fontify-keywords-region beg end))
1172 "Additional text properties managed by font-lock.
1173 This is used by `font-lock-default-unfontify-region' to decide
1179 font-lock-extra-managed-props
1184 ;; Called when any modification is made to buffer text.
1191 beg end old-len))))
1194 ;; Fontify the region the major mode has specified.
1196 ;; Fontify the whole lines which enclose the region.
1197 ;; Actually, this is not needed because
1198 ;; font-lock-default-fontify-region already rounds up to a whole
1199 ;; number of lines.
1200 ;; (setq beg (progn (goto-char beg) (line-beginning-position))
1201 ;; end (progn (goto-char end) (line-beginning-position 2)))
1203 ;; Rounding up to a whole number of lines should include the
1204 ;; line right after `end'. Typical case: the first char of
1205 ;; the line was deleted. Or a \n was inserted in the middle
1206 ;; of a line.
1212 "Function meant for `jit-lock-after-change-extend-region-functions'.
1213 This function does 2 things:
1214 - extend the region so that it not only includes the part that was modified
1215 but also the surrounding text whose highlighting may change as a consequence.
1216 - anticipate (part of) the region extension that will happen later in
1217 `font-lock-default-fontify-region', in order to avoid the need for
1218 double-redisplay in `jit-lock-fontify-now'."
1220 ;; First extend the region as font-lock-after-change-function would.
1223 beg end old-len))))
1227 ;; Then extend the region obeying font-lock-multiline properties,
1228 ;; indicating which part of the buffer needs to be refontified.
1229 ;; !!! This is the *main* user of font-lock-multiline property !!!
1230 ;; font-lock-after-change-function could/should also do that, but it
1231 ;; doesn't need to because font-lock-default-fontify-region does
1232 ;; it anyway. Here OTOH we have no guarantee that
1233 ;; font-lock-default-fontify-region will be executed on this region
1234 ;; any time soon.
1235 ;; Note: contrary to font-lock-default-fontify-region, we do not do
1236 ;; any loop here because we are not looking for a safe spot: we just
1237 ;; mark the text whose appearance may need to change as a result of
1238 ;; the buffer modification.
1250 ;; Rounding up to a whole number of lines should include the
1251 ;; line right after `end'. Typical case: the first char of
1252 ;; the line was deleted. Or a \n was inserted in the middle
1253 ;; of a line.
1255 ;; Finally, pre-enlarge the region to a whole number of lines, to try
1256 ;; and anticipate what font-lock-default-fontify-region will do, so as to
1257 ;; avoid double-redisplay.
1258 ;; We could just run `font-lock-extend-region-functions', but since
1259 ;; the only purpose is to avoid the double-redisplay, we prefer to
1260 ;; do here only the part that is cheap and most likely to be useful.
1262 font-lock-extend-region-functions)
1271 "Fontify some lines the way `font-lock-fontify-buffer' would.
1272 The lines could be a function or paragraph, or a specified number of lines.
1273 If ARG is given, fontify that many lines before and after point, or 16 lines if
1274 no ARG is given and `font-lock-mark-block-function' is nil.
1275 If `font-lock-mark-block-function' non-nil and no ARG is given, it is used to
1276 delimit the region to fontify."
1279 deactivate-mark)
1280 ;; Make sure we have the right `font-lock-keywords' etc.
1294 ;;; End of Fontification functions.
1295 \f
1296 ;;; Additional text property functions.
1298 ;; The following text property functions should be builtins. This means they
1299 ;; should be written in C and put with all the other text property functions.
1300 ;; In the meantime, those that are used by font-lock.el are defined in Lisp
1301 ;; below and given a `font-lock-' prefix. Those that are not used are defined
1302 ;; in Lisp below and commented out. sm.
1305 "Prepend to one property of the text from START to END.
1306 Arguments PROP and VALUE specify the property and value to prepend to the value
1307 already in place. The resulting property values are always lists.
1308 Optional argument OBJECT is the string or buffer containing the text."
1313 ;; Canonicalize old forms of face property.
1321 object)
1325 "Append to one property of the text from START to END.
1326 Arguments PROP and VALUE specify the property and value to append to the value
1327 already in place. The resulting property values are always lists.
1328 Optional argument OBJECT is the string or buffer containing the text."
1333 ;; Canonicalize old forms of face property.
1341 object)
1345 "Fill in one property of the text from START to END.
1346 Arguments PROP and VALUE specify the property and value to put where none are
1347 already in place. Therefore existing property values are not overwritten.
1348 Optional argument OBJECT is the string or buffer containing the text."
1355 ;; For completeness: this is to `remove-text-properties' as `put-text-property'
1356 ;; is to `add-text-properties', etc.
1357 ;;(defun remove-text-property (start end property &optional object)
1358 ;; "Remove a property from text from START to END.
1359 ;;Argument PROPERTY is the property to remove.
1360 ;;Optional argument OBJECT is the string or buffer containing the text.
1361 ;;Return t if the property was actually removed, nil otherwise."
1362 ;; (remove-text-properties start end (list property) object))
1364 ;; For consistency: maybe this should be called `remove-single-property' like
1365 ;; `next-single-property-change' (not `next-single-text-property-change'), etc.
1366 ;;(defun remove-single-text-property (start end prop value &optional object)
1367 ;; "Remove a specific property value from text from START to END.
1368 ;;Arguments PROP and VALUE specify the property and value to remove. The
1369 ;;resulting property values are not equal to VALUE nor lists containing VALUE.
1370 ;;Optional argument OBJECT is the string or buffer containing the text."
1371 ;; (let ((start (text-property-not-all start end prop nil object)) next prev)
1372 ;; (while start
1373 ;; (setq next (next-single-property-change start prop object end)
1374 ;; prev (get-text-property start prop object))
1375 ;; (cond ((and (symbolp prev) (eq value prev))
1376 ;; (remove-text-property start next prop object))
1377 ;; ((and (listp prev) (memq value prev))
1378 ;; (let ((new (delq value prev)))
1379 ;; (cond ((null new)
1380 ;; (remove-text-property start next prop object))
1381 ;; ((= (length new) 1)
1382 ;; (put-text-property start next prop (car new) object))
1383 ;; (t
1384 ;; (put-text-property start next prop new object))))))
1385 ;; (setq start (text-property-not-all next end prop nil object)))))
1387 ;;; End of Additional text property functions.
1388 \f
1389 ;;; Syntactic regexp fontification functions.
1391 ;; These syntactic keyword pass functions are identical to those keyword pass
1392 ;; functions below, with the following exceptions; (a) they operate on
1393 ;; `font-lock-syntactic-keywords' of course, (b) they are all `defun' as speed
1394 ;; is less of an issue, (c) eval of property value does not occur JIT as speed
1395 ;; is less of an issue, (d) OVERRIDE cannot be `prepend' or `append' as it
1396 ;; makes no sense for `syntax-table' property values, (e) they do not do it
1397 ;; LOUDLY as it is not likely to be intensive.
1400 "Apply HIGHLIGHT following a match.
1401 HIGHLIGHT should be of the form MATCH-HIGHLIGHT,
1402 see `font-lock-syntactic-keywords'."
1408 ;; No match but we might not signal an error.
1414 ;; Flush the syntax-cache. I believe this is not necessary for
1415 ;; font-lock's use of syntax-ppss, but I'm not 100% sure and it can
1416 ;; still be necessary for other users of syntax-ppss anyway.
1420 ;; Cannot override existing fontification.
1424 ;; Override existing fontification.
1427 ;; Keep existing fontification.
1431 "Fontify according to KEYWORDS until LIMIT.
1432 KEYWORDS should be of the form MATCH-ANCHORED, see `font-lock-keywords',
1433 LIMIT can be modified by the value of its PRE-MATCH-FORM."
1435 ;; Evaluate PRE-MATCH-FORM.
1437 ;; Set LIMIT to value of PRE-MATCH-FORM or the end of line.
1442 ;; Find an occurrence of `matcher' before `limit'.
1446 ;; Apply each highlight to this instance of `matcher'.
1451 ;; Evaluate POST-MATCH-FORM.
1455 "Fontify according to `font-lock-syntactic-keywords' between START and END.
1456 START should be at the beginning of a line."
1457 ;; Ensure the beginning of the file is properly syntactic-fontified.
1462 ;; If `font-lock-syntactic-keywords' is a symbol, get the real keywords.
1465 font-lock-syntactic-keywords)))
1466 ;; If `font-lock-syntactic-keywords' is not compiled, compile it.
1469 font-lock-syntactic-keywords
1470 t)))
1471 ;; Get down to business.
1474 keyword matcher highlights)
1476 ;; Find an occurrence of `matcher' from `start' to `end'.
1483 ;; Apply each highlight to this instance of `matcher', which may be
1484 ;; specific highlights or more keywords anchored to `matcher'.
1490 end))
1494 ;;; End of Syntactic regexp fontification functions.
1495 \f
1496 ;;; Syntactic fontification functions.
1505 "Put proper face on each string and comment between START and END.
1506 START should be at the beginning of a line."
1511 state face beg)
1514 ;;
1515 ;; Find the `start' state.
1517 ;;
1518 ;; Find each interesting place between here and `end'.
1529 comment-start-skip))
1530 ;; Find the comment delimiters
1531 ;; and use font-lock-comment-delimiter-face for them.
1535 comment-start-skip))
1537 font-lock-comment-delimiter-face)))
1540 font-lock-comment-delimiter-face))))
1545 ;;; End of Syntactic fontification functions.
1546 \f
1547 ;;; Keyword regexp fontification functions.
1550 "Apply HIGHLIGHT following a match.
1551 HIGHLIGHT should be of the form MATCH-HIGHLIGHT, see `font-lock-keywords'."
1556 ;; No match but we might not signal an error.
1565 ;; If `val' is nil, don't do anything. It is important to do it
1566 ;; explicitly, because when adding nil via things like
1567 ;; font-lock-append-text-property, the property is actually
1568 ;; changed from <face> to (<face>) which is undesirable. --Stef
1569 nil)
1571 ;; Cannot override existing fontification.
1575 ;; Override existing fontification.
1578 ;; Prepend to existing fontification.
1581 ;; Append to existing fontification.
1584 ;; Keep existing fontification.
1588 "Fontify according to KEYWORDS until LIMIT.
1589 KEYWORDS should be of the form MATCH-ANCHORED, see `font-lock-keywords',
1590 LIMIT can be modified by the value of its PRE-MATCH-FORM."
1593 ;; Evaluate PRE-MATCH-FORM.
1595 ;; Set LIMIT to value of PRE-MATCH-FORM or the end of line.
1600 ;; this is a multiline anchored match
1601 ;; (setq font-lock-multiline t)
1605 limit
1608 ;; Find an occurrence of `matcher' before `limit'.
1613 ;; Apply each highlight to this instance of `matcher'.
1618 ;; Evaluate POST-MATCH-FORM.
1622 "Fontify according to `font-lock-keywords' between START and END.
1623 START should be at the beginning of a line.
1624 LOUDLY, if non-nil, allows progress-meter bar."
1632 keyword matcher highlights)
1633 ;;
1634 ;; Fontify each item in `font-lock-keywords' from `start' to `end'.
1638 ;;
1639 ;; Find an occurrence of `matcher' from `start' to `end'.
1646 ;; Beware empty string matches since they will
1647 ;; loop indefinitely.
1654 ;; this is a multiline regexp match
1655 ;; (setq font-lock-multiline t)
1664 ;; Apply each highlight to this instance of `matcher', which may be
1665 ;; specific highlights or more keywords anchored to `matcher'.
1672 ;; Ensure forward progress. `pos' is a marker because anchored
1673 ;; keyword may add/delete text (this happens e.g. in grep.el).
1679 ;;; End of Keyword regexp fontification functions.
1680 \f
1681 ;; Various functions.
1684 "Compile KEYWORDS into the form (t KEYWORDS COMPILED...)
1685 Here each COMPILED is of the form (MATCHER HIGHLIGHT ...) as shown in the
1686 `font-lock-keywords' doc string.
1687 If SYNTACTIC-KEYWORDS is non-nil, it means these keywords are used for
1688 `font-lock-syntactic-keywords' rather than for `font-lock-keywords'."
1690 ;; This should never happen. But some external packages sometimes
1691 ;; call font-lock in unexpected and incorrect ways. It's important to
1692 ;; stop processing at this point, otherwise we may end up changing the
1693 ;; global value of font-lock-keywords and break highlighting in many
1694 ;; other buffers.
1697 keywords
1704 syntax-begin-function)))
1708 ;; Try to detect when a string or comment contains something that
1709 ;; looks like a defun and would thus confuse font-lock.
1717 font-lock-comment-face))
1720 prepend)))))
1721 keywords))
1729 ;; If FORM is a FACENAME then quote it. Otherwise ignore the quote.
1740 keyword)))
1743 "Evalulate KEYWORDS if a function (funcall) or variable (eval) name."
1745 keywords
1751 "Return value in ALIST for `major-mode', or ALIST if it is not an alist.
1752 Structure is ((MAJOR-MODE . VALUE) ...) where MAJOR-MODE may be t."
1755 alist))
1758 "Return LEVELth element of KEYWORDS.
1759 A LEVEL of nil is equal to a LEVEL of 0, a LEVEL of t is equal to
1760 \(1- (length KEYWORDS))."
1762 keywords)
1773 "Restart fontification in current buffer after recomputing from defaults.
1774 Recompute fontification variables using `font-lock-defaults' (or,
1775 if nil, using `font-lock-defaults-alist') and
1776 `font-lock-maximum-decoration'. Then restart fontification.
1778 Use this function when you have changed any of the above
1779 variables directly.
1781 Note: This function will erase modifications done by
1782 `font-lock-add-keywords' or `font-lock-remove-keywords', but will
1783 preserve `hi-lock-mode' highlighting patterns."
1794 "Set fontification defaults appropriately for this mode.
1795 Sets various variables using `font-lock-defaults' (or, if nil, using
1796 `font-lock-defaults-alist') and `font-lock-maximum-decoration'."
1797 ;; Set fontification defaults if not previously set for correct major mode.
1807 font-lock-defaults-alist)))))
1815 ;; Syntactic fontification?
1819 ;; Case fold during regexp fontification?
1823 ;; Syntax table for regexp and syntactic fontification?
1829 ;; The character to modify may be a single CHAR or a STRING.
1835 ;; Syntax function for syntactic fontification?
1840 ;; Variable alist?
1843 ;; Set up `font-lock-keywords' last because its value might depend
1844 ;; on other settings (e.g. font-lock-compile-keywords uses
1845 ;; font-lock-beginning-of-syntax-function).
1848 ;; Local fontification?
1854 ;; Now compile the keywords.
1858 \f
1859 ;;; Color etc. support.
1861 ;; Note that `defface' will not overwrite any faces declared above via
1862 ;; `custom-declare-face'.
1879 )
1881 "Font Lock mode face used to highlight comments."
1892 "Font Lock mode face used to highlight comment delimiters."
1904 "Font Lock mode face used to highlight strings."
1909 "Font Lock mode face used to highlight documentation."
1921 "Font Lock mode face used to highlight keywords."
1933 "Font Lock mode face used to highlight builtins."
1943 "Font Lock mode face used to highlight function names."
1957 "Font Lock mode face used to highlight variable names."
1969 "Font Lock mode face used to highlight type and classes."
1983 "Font Lock mode face used to highlight constants and labels."
1993 "Font Lock mode face used to highlight warnings."
1998 "Font Lock mode face used to highlight easy to overlook negation."
2003 "Font Lock mode face used to highlight preprocessor directives."
2008 "Font Lock mode face for backslashes in Lisp regexp grouping constructs."
2013 "Font Lock mode face used to highlight grouping constructs in Lisp regexps."
2016 ;;; End of Color etc. support.
2017 \f
2018 ;;; Menu support.
2020 ;; This section of code is commented out because Emacs does not have real menu
2021 ;; buttons. (We can mimic them by putting "( ) " or "(X) " at the beginning of
2022 ;; the menu entry text, but with Xt it looks both ugly and embarrassingly
2023 ;; amateur.) If/When Emacs gets real menus buttons, put in menu-bar.el after
2024 ;; the entry for "Text Properties" something like:
2025 ;;
2026 ;; (define-key menu-bar-edit-menu [font-lock]
2027 ;; (cons "Syntax Highlighting" font-lock-menu))
2028 ;;
2029 ;; and remove a single ";" from the beginning of each line in the rest of this
2030 ;; section. Probably the mechanism for telling the menu code what are menu
2031 ;; buttons and when they are on or off needs tweaking. I have assumed that the
2032 ;; mechanism is via `menu-toggle' and `menu-selected' symbol properties. sm.
2034 ;;;;;###autoload
2035 ;;(progn
2036 ;; ;; Make the Font Lock menu.
2037 ;; (defvar font-lock-menu (make-sparse-keymap "Syntax Highlighting"))
2038 ;; ;; Add the menu items in reverse order.
2039 ;; (define-key font-lock-menu [fontify-less]
2040 ;; '("Less In Current Buffer" . font-lock-fontify-less))
2041 ;; (define-key font-lock-menu [fontify-more]
2042 ;; '("More In Current Buffer" . font-lock-fontify-more))
2043 ;; (define-key font-lock-menu [font-lock-sep]
2044 ;; '("--"))
2045 ;; (define-key font-lock-menu [font-lock-mode]
2046 ;; '("In Current Buffer" . font-lock-mode))
2047 ;; (define-key font-lock-menu [global-font-lock-mode]
2048 ;; '("In All Buffers" . global-font-lock-mode)))
2049 ;;
2050 ;;;;;###autoload
2051 ;;(progn
2052 ;; ;; We put the appropriate `menu-enable' etc. symbol property values on when
2053 ;; ;; font-lock.el is loaded, so we don't need to autoload the three variables.
2054 ;; (put 'global-font-lock-mode 'menu-toggle t)
2055 ;; (put 'font-lock-mode 'menu-toggle t)
2056 ;; (put 'font-lock-fontify-more 'menu-enable '(identity))
2057 ;; (put 'font-lock-fontify-less 'menu-enable '(identity)))
2058 ;;
2059 ;; ;; Put the appropriate symbol property values on now. See above.
2060 ;;(put 'global-font-lock-mode 'menu-selected 'global-font-lock-mode)
2061 ;;(put 'font-lock-mode 'menu-selected 'font-lock-mode)
2062 ;;(put 'font-lock-fontify-more 'menu-enable '(nth 2 font-lock-fontify-level))
2063 ;;(put 'font-lock-fontify-less 'menu-enable '(nth 1 font-lock-fontify-level))
2064 ;;
2065 ;;(defvar font-lock-fontify-level nil) ; For less/more fontification.
2066 ;;
2067 ;;(defun font-lock-fontify-level (level)
2068 ;; (let ((font-lock-maximum-decoration level))
2069 ;; (when font-lock-mode
2070 ;; (font-lock-mode))
2071 ;; (font-lock-mode)
2072 ;; (when font-lock-verbose
2073 ;; (message "Fontifying %s... level %d" (buffer-name) level))))
2074 ;;
2075 ;;(defun font-lock-fontify-less ()
2076 ;; "Fontify the current buffer with less decoration.
2077 ;;See `font-lock-maximum-decoration'."
2078 ;; (interactive)
2079 ;; ;; Check in case we get called interactively.
2080 ;; (if (nth 1 font-lock-fontify-level)
2081 ;; (font-lock-fontify-level (1- (car font-lock-fontify-level)))
2082 ;; (error "No less decoration")))
2083 ;;
2084 ;;(defun font-lock-fontify-more ()
2085 ;; "Fontify the current buffer with more decoration.
2086 ;;See `font-lock-maximum-decoration'."
2087 ;; (interactive)
2088 ;; ;; Check in case we get called interactively.
2089 ;; (if (nth 2 font-lock-fontify-level)
2090 ;; (font-lock-fontify-level (1+ (car font-lock-fontify-level)))
2091 ;; (error "No more decoration")))
2092 ;;
2093 ;; ;; This should be called by `font-lock-set-defaults'.
2094 ;;(defun font-lock-set-menu ()
2095 ;; ;; Activate less/more fontification entries if there are multiple levels for
2096 ;; ;; the current buffer. Sets `font-lock-fontify-level' to be of the form
2097 ;; ;; (CURRENT-LEVEL IS-LOWER-LEVEL-P IS-HIGHER-LEVEL-P) for menu activation.
2098 ;; (let ((keywords (or (nth 0 font-lock-defaults)
2099 ;; (nth 1 (assq major-mode font-lock-defaults-alist))))
2100 ;; (level (font-lock-value-in-major-mode font-lock-maximum-decoration)))
2101 ;; (make-local-variable 'font-lock-fontify-level)
2102 ;; (if (or (symbolp keywords) (= (length keywords) 1))
2103 ;; (font-lock-unset-menu)
2104 ;; (cond ((eq level t)
2105 ;; (setq level (1- (length keywords))))
2106 ;; ((or (null level) (zerop level))
2107 ;; ;; The default level is usually, but not necessarily, level 1.
2108 ;; (setq level (- (length keywords)
2109 ;; (length (member (eval (car keywords))
2110 ;; (mapcar 'eval (cdr keywords))))))))
2111 ;; (setq font-lock-fontify-level (list level (> level 1)
2112 ;; (< level (1- (length keywords))))))))
2113 ;;
2114 ;; ;; This should be called by `font-lock-unset-defaults'.
2115 ;;(defun font-lock-unset-menu ()
2116 ;; ;; Deactivate less/more fontification entries.
2117 ;; (setq font-lock-fontify-level nil))
2119 ;;; End of Menu support.
2120 \f
2121 ;;; Various regexp information shared by several modes.
2122 ;; ;; Information specific to a single mode should go in its load library.
2124 ;; Font Lock support for C, C++, Objective-C and Java modes is now in
2125 ;; cc-fonts.el (and required by cc-mode.el). However, the below function
2126 ;; should stay in font-lock.el, since it is used by other libraries. sm.
2129 "Match, and move over, any declaration/definition item after point.
2130 Matches after point, but ignores leading whitespace and `*' characters.
2131 Does not move further than LIMIT.
2133 The expected syntax of a declaration/definition item is `word' (preceded by
2134 optional whitespace and `*' characters and proceeded by optional whitespace)
2135 optionally followed by a `('. Everything following the item (but belonging to
2136 it) is expected to be skip-able by `scan-sexps', and items are expected to be
2137 separated with a `,' and to be terminated with a `;'.
2139 Thus the regexp matches after point: word (
2140 ^^^^ ^
2141 Where the match subexpressions are: 1 2
2143 The item is delimited by (match-beginning 1) and (match-end 1).
2144 If (match-beginning 2) is non-nil, the item is followed by a `('.
2146 This function could be MATCHER in a MATCH-ANCHORED `font-lock-keywords' item."
2149 ;; If `word' is followed by a double open-paren, it's probably
2150 ;; a macro used for "int myfun P_ ((int arg1))". Let's go back one
2151 ;; word to try and match `myfun' rather than `P_'.
2156 ;; Looks like it was something else, so go back to where we
2157 ;; were and reset the match data by rematching.
2163 ;; Restrict to the LIMIT.
2166 ;; Move over any item value, etc., to the next item.
2173 ;; C preprocessor(cpp) is used outside of C, C++ and Objective-C source file.
2174 ;; e.g. assembler code and GNU linker script in Linux kernel.
2175 ;; `cpp-font-lock-keywords' is handy for modes for the files.
2176 ;;
2177 ;; Here we cannot use `regexp-opt' because because regex-opt is not preloaded
2178 ;; while font-lock.el is preloaded to emacs. So values pre-calculated with
2179 ;; regexp-opt are used here.
2181 ;; `cpp-font-lock-keywords-source-directives' is calculated from:
2182 ;;
2183 ;; (regexp-opt
2184 ;; '("define" "elif" "else" "endif" "error" "file" "if" "ifdef"
2185 ;; "ifndef" "import" "include" "line" "pragma" "undef" "warning"))
2186 ;;
2188 "define\\|e\\(?:l\\(?:if\\|se\\)\\|ndif\\|rror\\)\\|file\\|i\\(?:f\\(?:n?def\\)?\\|mport\\|nclude\\)\\|line\\|pragma\\|undef\\|warning"
2191 ;; `cpp-font-lock-keywords-source-depth' is calculated from:
2192 ;;
2193 ;; (regexp-opt-depth (regexp-opt
2194 ;; '("define" "elif" "else" "endif" "error" "file" "if" "ifdef"
2195 ;; "ifndef" "import" "include" "line" "pragma" "undef" "warning")))
2196 ;;
2198 "An integer representing regular expression depth of `cpp-font-lock-keywords-source-directives'.
2205 ;;
2206 ;; Fontify error directives.
2208 ;;
2209 ;; Fontify filenames in #include <...> preprocessor directives as strings.
2212 ;;
2213 ;; Fontify function macro names.
2216 ;;
2217 ;; Macro arguments.
2222 limit)
2223 t))
2225 ;;
2226 ;; Fontify symbol names in #elif or #if ... defined preprocessor directives.
2230 ;;
2231 ;; Fontify otherwise as symbol names, and the preprocessor directive names.
2238 "Font lock keywords for C preprocessor directives.
2239 `c-mode', `c++-mode' and `objc-mode' have their own font lock keywords
2240 for C preprocessor directives. This definition is for the other modes
2241 in which C preprocessor directives are used. e.g. `asm-mode' and
2244 \f
2245 ;; Lisp.
2251 ;; Function declarations.
2258 ;; Variable declarations.
2260 ;; Structure declarations.
2263 ;; Any whitespace and defined object.
2270 nil t))
2271 ;; Emacs Lisp autoload cookies. Supports the slightly different
2272 ;; forms used by mh-e, calendar, etc.
2274 ;; Regexp negated char group.
2301 ;; Control structures. Common Lisp forms.
2322 ;; Exit/Feature symbols as constants.
2327 ;; Erroneous structures.
2328 ("(\\(abort\\|assert\\|warn\\|check-type\\|cerror\\|error\\|signal\\)\\>" 1 font-lock-warning-face)
2329 ;; Words inside \\[] tend to be for `substitute-command-keys'.
2331 ;; Words inside `' tend to be symbol names.
2333 ;; Constant values.
2335 ;; ELisp and CLisp `&' keywords as types.
2337 ;; ELisp regexp grouping constructs
2340 ;; The following loop is needed to continue searching after matches
2341 ;; that do not occur in strings. The associated regexp matches one
2342 ;; of `\\\\' `\\(' `\\(?:' `\\|' `\\)'. `\\\\' has been included to
2343 ;; avoid highlighting, for example, `\\(' in `\\\\('.
2344 (while (re-search-forward "\\(\\\\\\\\\\)\\(?:\\(\\\\\\\\\\)\\|\\((\\(?:\\?[0-9]*:\\)?\\|[|)]\\)\\)" bound t)
2353 ;;; This is too general -- rms.
2354 ;;; A user complained that he has functions whose names start with `do'
2355 ;;; and that they get the wrong color.
2356 ;;; ;; CL `with-' and `do-' constructs
2357 ;;; ("(\\(\\(do-\\|with-\\)\\(\\s_\\|\\w\\)*\\)" 1 font-lock-keyword-face)
2358 )))
2363 \f
2366 ;; arch-tag: 682327e4-64d8-4057-b20b-1fbb9f1fc54c
2367 ;;; font-lock.el ends here