diff options
| author | Karl Heuer <kwzh@gnu.org> | 1996-01-04 23:35:58 +0000 |
|---|---|---|
| committer | Karl Heuer <kwzh@gnu.org> | 1996-01-04 23:35:58 +0000 |
| commit | d9f7b2d33c63213453ff3312e5bb9bb446476ca7 (patch) | |
| tree | b2f8ed770e8b6bc5a6d29eb5f8f22f87d9ff5ab1 /lisp | |
| parent | 5512735ef6aeed000bedb1b313b1c30176fdebcb (diff) | |
| download | emacs-d9f7b2d33c63213453ff3312e5bb9bb446476ca7.tar.gz | |
(font-lock-keywords): Doc fix.
Diffstat (limited to 'lisp')
| -rw-r--r-- | lisp/font-lock.el | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/lisp/font-lock.el b/lisp/font-lock.el index a4eab49b9cb..3c44bc89c36 100644 --- a/lisp/font-lock.el +++ b/lisp/font-lock.el @@ -149,7 +149,7 @@ Each element should be of the form: where HIGHLIGHT should be either MATCH-HIGHLIGHT or MATCH-ANCHORED. For highlighting single items, typically only MATCH-HIGHLIGHT is required. -However, if an item or (typically) items is to be hightlighted following the +However, if an item or (typically) items are to be highlighted following the instance of another item (the anchor) then MATCH-ANCHORED may be required. MATCH-HIGHLIGHT should be of the form: @@ -166,7 +166,7 @@ OVERRIDE and LAXMATCH are flags. If OVERRIDE is t, existing fontification may 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, no error is signalled if there is no MATCH in MATCHER. +If LAXMATCH is non-nil, no error is signaled if there is no MATCH in MATCHER. For example, an element of the form highlights (if not already highlighted): |