view BUGS @ 29799:baa52c9029f6

(with-buffer-prepared-for-jit-lock): Renamed from with-buffer-prepared-for-font-lock and use inhibit-modification-hooks rather than setting *-change-functions. Update all functions to use the new name. (jit-lock-first-unfontify-pos): New semantics (and doc). (jit-lock-mode): Make non-interactive. Don't automatically turn on font-lock. Set jit-lock-first-unfontify-pos to indicate deferred-contextual mode. Always use jit-lock-after-change. Remove and restore font-lock-after-change-function. (turn-on-jit-lock, jit-lock-after-fontify-buffer) (jit-lock-after-unfontify-buffer): Remove. (jit-lock-stealth-fontify): Reset jit-lock-first-unfontify-pos to point-max rather than to nil. (jit-lock-after-change): Set the `fontified' text-prop to nil.
author Stefan Monnier <monnier@iro.umontreal.ca>
date Tue, 20 Jun 2000 16:24:04 +0000
parents 354e0c45cedf
children af68d12218d0
line wrap: on
line source

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,"