view BUGS @ 27636:161ec77aa308

(font-lock-keywords): Fix doc for multiline matches. (font-lock-add-keywords): Make it work even if font-lock-mode is nil, so that it can be used more easily in <foo>-mode-hook. Also make sure to avoid duplicate entries. (font-lock-update-removed-keyword-alist): Renamed `major-mode'->`mode'. (font-lock-remove-keywords): Just as was done for `add', allow it to work even if font-lock-mode is nil. Also make sure we don't modify any pre-existing list by forcing a copy-sequence. Finally rename `major-mode' to `mode'. (font-lock-fontify-syntactic-anchored-keywords) (font-lock-fontify-anchored-keywords) (font-lock-fontify-keywords-region): Use line-end-position. Don't make `font-lock-multiline' local (it's now done in font-lock-set-defaults). (font-lock-set-defaults): Make `font-lock-multiline' local. Also move the `font-lock-fontified' creation to inside the `unless'.

If you think you may have found a bug in GNU Emacs, please
read the Bugs section of the Emacs manual for advice on
(1) how to tell when to report a bug, and
(2) how to write a useful bug report and what information
it needs to have.

There are three ways to read the Bugs section.

(1) In a printed copy of the Emacs manual.
You can order one from the Free Software Foundation;
see the file etc/ORDERS.  But if you don't have a copy on
hand and you think you have found a bug, you shouldn't wait
to get a printed manual; you should read the section right away
as described below.

(2) With Info.  Start Emacs, do C-h i to enter Info,
then m Emacs RET to get to the Emacs manual, then m Bugs RET
to get to the section on bugs.  Or use standalone Info in
a like manner.  (Standalone Info is part of the Texinfo distribution,
not part of the Emacs distribution.)

(3) By hand.  Do
    cat info/emacs* | more "+/^File: emacs,  Node: Bugs,"