?
Current Path : /usr/share/emacs/24.3/lisp/ |
Linux gator3171.hostgator.com 4.19.286-203.ELK.el7.x86_64 #1 SMP Wed Jun 14 04:33:55 CDT 2023 x86_64 |
Current File : //usr/share/emacs/24.3/lisp/font-lock.elc |
;ELC ;;; Compiled by mockbuild@buildfarm06-new.corp.cloudlinux.com on Fri Oct 11 10:12:50 2024 ;;; from file /builddir/build/BUILD/emacs-24.3/lisp/font-lock.el ;;; in Emacs version 24.3 ;;; with all optimizations. ;;; This file uses dynamic docstrings, first added in Emacs 19.29. ;;; This file does not contain utf-8 non-ASCII characters, ;;; and so can be loaded in Emacs versions earlier than 23. ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; (byte-code "\300\301!\210\302\303\304\305\306\307\306\310\311\312& \210\302\313\314\315\316\317\311\303&\210\302\320\314\321\311\303%\210\322\323\324\325\326\327\311\303&\210\330\323\314\331#\210\322\332\333\334\326\335\311\303&\210\322\336\314\337\326\340\311\303\341\331& \207" [require syntax custom-declare-group font-lock ((jit-lock custom-group)) "Font Lock mode text highlighting package." :link (custom-manual :tag "Emacs Manual" "(emacs)Font Lock") (custom-manual :tag "Elisp Manual" "(elisp)Font Lock Mode") :group faces font-lock-faces nil "Faces for highlighting text." :prefix "font-lock-" font-lock-extra-types "Extra mode-specific type names for highlighting declarations." custom-declare-variable font-lock-maximum-size 256000 "Maximum buffer size for unsupported buffer fontification.\nWhen `font-lock-support-mode' is nil, only buffers smaller than\nthis are fontified. This variable has no effect if a Font Lock\nsupport mode (usually `jit-lock-mode') is enabled.\n\nIf nil, means size is irrelevant.\nIf a list, each element should be a cons pair of the form (MAJOR-MODE . SIZE),\nwhere MAJOR-MODE is a symbol or t (meaning the default). For example:\n ((c-mode . 256000) (c++-mode . 256000) (rmail-mode . 1048576))\nmeans that the maximum size is 250K for buffers in C or C++ modes, one megabyte\nfor buffers in Rmail mode, and size is irrelevant otherwise." :type (choice (const :tag "none" nil) (integer :tag "size") (repeat :menu-tag "mode specific" :tag "mode specific" :value ((t)) (cons :tag "Instance" (radio :tag "Mode" (const :tag "all" t) (symbol :tag "name")) (radio :tag "Size" (const :tag "none" nil) (integer :tag "size"))))) make-obsolete-variable "24.1" font-lock-maximum-decoration t "Maximum decoration level for fontification.\nIf nil, use the default decoration (typically the minimum available).\nIf t, use the maximum decoration available.\nIf a number, use that level of decoration (or if not available the maximum).\nThe higher the number, the more decoration is done.\nIf a list, each element should be a cons pair of the form (MAJOR-MODE . LEVEL),\nwhere MAJOR-MODE is a symbol or t (meaning the default). For example:\n ((c-mode . t) (c++-mode . 2) (t . 1))\nmeans use the maximum decoration available for buffers in C mode, level 2\ndecoration for buffers in C++ mode, and level 1 decoration otherwise." (choice (const :tag "default" nil) (const :tag "maximum" t) (integer :tag "level" 1) (repeat :menu-tag "mode specific" :tag "mode specific" :value ((t . t)) (cons :tag "Instance" (radio :tag "Mode" (const :tag "all" t) (symbol :tag "name")) (radio :tag "Decoration" (const :tag "default" nil) (const :tag "maximum" t) (integer :tag "level" 1))))) font-lock-verbose "If non-nil, means show status messages for buffer fontification.\nIf a number, only buffers greater than this size have fontification messages." (choice (const :tag "never" nil) (other :tag "always" t) (integer :tag "size")) :version] 10) #@32 Face name to use for comments. (defvar font-lock-comment-face 'font-lock-comment-face (#$ . 3514)) #@42 Face name to use for comment delimiters. (defvar font-lock-comment-delimiter-face 'font-lock-comment-delimiter-face (#$ . 3619)) #@31 Face name to use for strings. (defvar font-lock-string-face 'font-lock-string-face (#$ . 3754)) #@37 Face name to use for documentation. (defvar font-lock-doc-face 'font-lock-doc-face (#$ . 3856)) #@32 Face name to use for keywords. (defvar font-lock-keyword-face 'font-lock-keyword-face (#$ . 3958)) #@32 Face name to use for builtins. (defvar font-lock-builtin-face 'font-lock-builtin-face (#$ . 4063)) #@38 Face name to use for function names. (defvar font-lock-function-name-face 'font-lock-function-name-face (#$ . 4168)) #@38 Face name to use for variable names. (defvar font-lock-variable-name-face 'font-lock-variable-name-face (#$ . 4291)) #@44 Face name to use for type and class names. (defvar font-lock-type-face 'font-lock-type-face (#$ . 4414)) #@48 Face name to use for constant and label names. (defvar font-lock-constant-face 'font-lock-constant-face (#$ . 4525)) #@52 Face name to use for things that should stand out. (defvar font-lock-warning-face 'font-lock-warning-face (#$ . 4648)) #@92 Face name to use for easy to overlook negation. This can be an "!" or the "n" in "ifndef". (defvar font-lock-negation-char-face 'font-lock-negation-char-face (#$ . 4773)) #@47 Face name to use for preprocessor directives. (defvar font-lock-preprocessor-face 'font-lock-preprocessor-face (#$ . 4950)) (byte-code "\302\303\304\305#\210\306\305\211\203, @\303N\203% \304N\204% \307\304\303N#\210 A\211\204 *\310\303\304\311#\207" [prop --dolist-tail-- defvaralias font-lock-reference-face font-lock-constant-face nil (saved-value saved-variable-comment) put make-obsolete-variable "20.3"] 6) #@5729 A list of the keywords to highlight. There are two kinds of values: user-level, and compiled. A user-level keywords list is what a major mode or the user would set up. Normally the list would come from `font-lock-defaults'. through selection of a fontification level and evaluation of any contained expressions. You can also alter it by calling `font-lock-add-keywords' or `font-lock-remove-keywords' with MODE = nil. Each element in a user-level keywords list should have one of these forms: MATCHER (MATCHER . SUBEXP) (MATCHER . FACENAME) (MATCHER . HIGHLIGHT) (MATCHER HIGHLIGHT ...) (eval . FORM) where MATCHER can be either the regexp to search for, or the function name to call to make the search (called with one argument, the limit of the search; it should return non-nil, move point, and set `match-data' appropriately if it succeeds; like `re-search-forward' would). MATCHER regexps can be generated via the function `regexp-opt'. FORM is an expression, whose value should be a keyword element, evaluated when the keyword is (first) used in a buffer. This feature can be used to provide a keyword that can only be generated when Font Lock mode is actually turned on. HIGHLIGHT should be either MATCH-HIGHLIGHT or MATCH-ANCHORED. For highlighting single items, for example each instance of the word "foo", typically only MATCH-HIGHLIGHT is required. However, if an item or (typically) items are to be highlighted following the instance of another item (the anchor), for example each instance of the word "bar" following the word "anchor" then MATCH-ANCHORED may be required. MATCH-HIGHLIGHT should be of the form: (SUBEXP FACENAME [OVERRIDE [LAXMATCH]]) SUBEXP is the number of the subexpression of MATCHER to be highlighted. FACENAME is an expression whose value is the face name to use. Instead of a face, FACENAME can evaluate to a property list of the form (face FACE PROP1 VAL1 PROP2 VAL2 ...) in which case all the listed text-properties will be set rather than just FACE. In such a case, you will most likely want to put those properties in `font-lock-extra-managed-props' or to override `font-lock-unfontify-region-function'. OVERRIDE and LAXMATCH are flags. If OVERRIDE is t, existing fontification can be overwritten. If `keep', only parts not already fontified are highlighted. If `prepend' or `append', existing fontification is merged with the new, in which the new or existing fontification, respectively, takes precedence. If LAXMATCH is non-nil, that means don't signal an error if there is no match for SUBEXP in MATCHER. For example, an element of the form highlights (if not already highlighted): "\\\=<foo\\\=>" discrete occurrences of "foo" in the value of the variable `font-lock-keyword-face'. ("fu\\(bar\\)" . 1) substring "bar" within all occurrences of "fubar" in the value of `font-lock-keyword-face'. ("fubar" . fubar-face) Occurrences of "fubar" in the value of `fubar-face'. ("foo\\|bar" 0 foo-bar-face t) occurrences of either "foo" or "bar" in the value of `foo-bar-face', even if already highlighted. (fubar-match 1 fubar-face) the first subexpression within all occurrences of whatever the function `fubar-match' finds and matches in the value of `fubar-face'. MATCH-ANCHORED should be of the form: (MATCHER PRE-MATCH-FORM POST-MATCH-FORM MATCH-HIGHLIGHT ...) where MATCHER is a regexp to search for or the function name to call to make the search, as for MATCH-HIGHLIGHT above, but with one exception; see below. PRE-MATCH-FORM and POST-MATCH-FORM are evaluated before the first, and after the last, instance MATCH-ANCHORED's MATCHER is used. Therefore they can be used to initialize before, and cleanup after, MATCHER is used. Typically, PRE-MATCH-FORM is used to move to some position relative to the original MATCHER, before starting with MATCH-ANCHORED's MATCHER. POST-MATCH-FORM might be used to move back, before resuming with MATCH-ANCHORED's parent's MATCHER. For example, an element of the form highlights (if not already highlighted): ("\\\=<anchor\\\=>" (0 anchor-face) ("\\\=<item\\\=>" nil nil (0 item-face))) discrete occurrences of "anchor" in the value of `anchor-face', and subsequent discrete occurrences of "item" (on the same line) in the value of `item-face'. (Here PRE-MATCH-FORM and POST-MATCH-FORM are nil. Therefore "item" is initially searched for starting from the end of the match of "anchor", and searching for subsequent instances of "anchor" resumes from where searching for "item" concluded.) The above-mentioned exception is as follows. The limit of the MATCHER search defaults to the end of the line after PRE-MATCH-FORM is evaluated. However, if PRE-MATCH-FORM returns a position greater than the position after PRE-MATCH-FORM is evaluated, that position is used as the limit of the search. It is generally a bad idea to return a position greater than the end of the line, i.e., cause the MATCHER search to span lines. These regular expressions can match text which spans lines, although it is better to avoid it if possible since updating them while editing text is slower, and it is not guaranteed to be always correct when using support modes like jit-lock or lazy-lock. This variable is set by major modes via the variable `font-lock-defaults'. Be careful when composing regexps for this list; a poorly written pattern can dramatically slow things down! A compiled keywords list starts with t. It is produced internal by `font-lock-compile-keywords' from a user-level keywords list. Its second element is the user-level keywords list that was compiled. The remaining elements have the same form as user-level keywords, but normally their values have been optimized. (defvar font-lock-keywords nil (#$ . 5381)) #@555 Alist of additional `font-lock-keywords' elements for major modes. Each element has the form (MODE KEYWORDS . HOW). `font-lock-set-defaults' adds the elements in the list KEYWORDS to `font-lock-keywords' when Font Lock is turned on in major mode MODE. If HOW is nil, KEYWORDS are added at the beginning of `font-lock-keywords'. If it is `set', they are used to replace the value of `font-lock-keywords'. If HOW is any other non-nil value, they are added at the end. This is normally set via `font-lock-add-keywords' and `font-lock-remove-keywords'. (defvar font-lock-keywords-alist nil (#$ . 11160)) (put 'font-lock-keywords-alist 'risky-local-variable t) #@343 Alist of `font-lock-keywords' elements to be removed for major modes. Each element has the form (MODE . KEYWORDS). `font-lock-set-defaults' removes the elements in the list KEYWORDS from `font-lock-keywords' when Font Lock is turned on in major mode MODE. This is normally set via `font-lock-add-keywords' and `font-lock-remove-keywords'. (defvar font-lock-removed-keywords-alist nil (#$ . 11828)) #@112 Non-nil means Font Lock should not fontify comments or strings. This is normally set via `font-lock-defaults'. (defvar font-lock-keywords-only nil (#$ . 12236)) #@186 Non-nil means the patterns in `font-lock-keywords' are case-insensitive. This is set via the function `font-lock-set-defaults', based on the CASE-FOLD argument of `font-lock-defaults'. (defvar font-lock-keywords-case-fold-search nil (#$ . 12404)) (make-variable-buffer-local 'font-lock-keywords-case-fold-search) #@172 Point up to which `font-lock-syntactic-keywords' has been applied. If nil, this is ignored, in which case the syntactic fontification may sometimes be slightly incorrect. (defvar font-lock-syntactically-fontified 0 (#$ . 12724)) (make-variable-buffer-local 'font-lock-syntactically-fontified) #@285 Function to determine which face to use when fontifying syntactically. The function is called with a single parameter (the state as returned by `parse-partial-sexp' at the beginning of the region to highlight) and should return a face. This is normally set via `font-lock-defaults'. (defvar font-lock-syntactic-face-function #[(state) "\3038\203 \207\n\207" [state font-lock-string-face font-lock-comment-face 3] 2] (#$ . 13024)) #@1147 A list of the syntactic keywords to put syntax properties on. The value can be the list itself, or the name of a function or variable whose value is the list. See `font-lock-keywords' for a description of the form of this list; only the differences are stated here. MATCH-HIGHLIGHT should be of the form: (SUBEXP SYNTAX OVERRIDE LAXMATCH) where SYNTAX can be a string (as taken by `modify-syntax-entry'), a syntax table, a cons cell (as returned by `string-to-syntax') or an expression whose value is such a form. OVERRIDE cannot be `prepend' or `append'. Here are two examples of elements of `font-lock-syntactic-keywords' and what they do: ("\\$\\(#\\)" 1 ".") gives a hash character punctuation syntax (".") when following a dollar-sign character. Hash characters in other contexts will still follow whatever the syntax table says about the hash character. ("\\('\\).\\('\\)" (1 "\"") (2 "\"")) gives a pair single-quotes, which surround a single character, a SYNTAX of "\"" (meaning string quote syntax). Single-quote characters in other contexts will not be affected. This is normally set via `font-lock-defaults'. (defvar font-lock-syntactic-keywords nil (#$ . 13466)) (make-obsolete-variable 'font-lock-syntactic-keywords 'syntax-propertize-function "24.1") #@155 Non-nil means use this syntax table for fontifying. If this is nil, the major mode's syntax table is used. This is normally set via `font-lock-defaults'. (defvar font-lock-syntax-table nil (#$ . 14764)) #@568 Non-nil means use this function to move back outside all constructs. When called with no args it should move point backward to a place which is not in a string or comment and not within any bracket-pairs (or else, a place such that any bracket-pairs outside it can be ignored for Emacs syntax analysis and fontification). If this is nil, Font Lock uses `syntax-begin-function' to move back outside of any comment, string, or sexp. This variable is semi-obsolete; we recommend setting `syntax-begin-function' instead. This is normally set via `font-lock-defaults'. (defvar font-lock-beginning-of-syntax-function nil (#$ . 14974)) (make-obsolete-variable 'font-lock-beginning-of-syntax-function 'syntax-begin-function "23.3" 'set) #@221 Non-nil means use this function to mark a block of text. When called with no args it should leave point at the beginning of any enclosing textual block and mark at the end. This is normally set via `font-lock-defaults'. (defvar font-lock-mark-block-function nil (#$ . 15713)) #@91 Function to use for fontifying the buffer. This is normally set via `font-lock-defaults'. (defvar font-lock-fontify-buffer-function 'font-lock-default-fontify-buffer (#$ . 15995)) #@139 Function to use for unfontifying the buffer. This is used when turning off Font Lock mode. This is normally set via `font-lock-defaults'. (defvar font-lock-unfontify-buffer-function 'font-lock-default-unfontify-buffer (#$ . 16182)) #@254 Function to use for fontifying a region. It should take two args, the beginning and end of the region, and an optional third arg VERBOSE. If VERBOSE is non-nil, the function should print status messages. This is normally set via `font-lock-defaults'. (defvar font-lock-fontify-region-function 'font-lock-default-fontify-region (#$ . 16421)) #@153 Function to use for unfontifying a region. It should take two args, the beginning and end of the region. This is normally set via `font-lock-defaults'. (defvar font-lock-unfontify-region-function 'font-lock-default-unfontify-region (#$ . 16771)) #@204 List of Font Lock mode related modes that should not be turned on. Currently, valid mode names are `fast-lock-mode', `jit-lock-mode' and `lazy-lock-mode'. This is normally set via `font-lock-defaults'. (defvar font-lock-inhibit-thing-lock nil (#$ . 17024)) #@292 Whether font-lock should cater to multiline keywords. If nil, don't try to handle multiline patterns. If t, always handle multiline patterns. If `undecided', don't try to handle multiline patterns until you see one. Major/minor modes can set this variable if they know which option applies. (defvar font-lock-multiline nil (#$ . 17289)) (defvar font-lock-fontified nil) #@142 Return non-nil if the current buffer is ready for fontification. The MODE argument, if non-nil, means Font Lock mode is about to be enabled. (defalias 'font-lock-specified-p #[(mode) "\206$ \306\301!\203 \206$ \n\205$ \306\303!\205$ \205$ \f\205$ \f =?\207" [font-lock-defaults font-lock-keywords mode font-lock-set-defaults font-lock-major-mode major-mode boundp] 2 (#$ . 17666)]) (defalias 'font-lock-initial-fontify #[nil "\2050 \305\306!\2050 \307 !\203 \310\202/ \n\203! \n\311 V\203&