annotate BUGS @ 35926:d2997845573f

(hi-lock-mode): Toggling hi-lock-mode now affects all buffers. When hi-lock turned on rather than only checking current buffer for regexps, all buffers are checked. Moved activation of font-lock to hi-lock-refontify. When font-lock turned off rather than removing added highlighting just in current buffer, remove it in all buffers. Changed edit menu text from "Automatic Highlighting" to "Regexp Highlighting" Documentation for highlighting phrases, minor documentation changes. (hi-lock-set-file-patterns): Execute only if there are new or existing file patterns. (hi-lock-refontify): Assume font-lock-fontify-buffer will first unfontify and, if a support mode is active, will not refontify the whole buffer. If necessary, turn on font lock. (Removed font-lock-unfontify and font-lock support-mode-specific calls, such as lazy-lock-fontify-window.) (hi-lock-find-patterns): Do not turn on hi-lock-mode even if patterns are found. Not useful now since find-file-hook is removed if hi-lock is off, but may be needed for per-buffer hi-lock activation. (hi-lock-face-phrase-buffer): New function. Also added related menu item and keybinding. (highlight-phrase): New alias, to hi-lock-face-phrase-buffer. (hi-lock-process-phrase): New function. (hi-lock-line-face-buffer): Doc fixes. (hi-lock-face-buffer): Doc fixes. (hi-lock-unface-buffer): Doc fixes.
author Gerd Moellmann <gerd@gnu.org>
date Tue, 06 Feb 2001 15:43:37 +0000
parents af68d12218d0
children 8ce686bd7f4f
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
rev   line source
25856
Dave Love <fx@gnu.org>
parents:
diff changeset
1 If you think you may have found a bug in GNU Emacs, please
Dave Love <fx@gnu.org>
parents:
diff changeset
2 read the Bugs section of the Emacs manual for advice on
Dave Love <fx@gnu.org>
parents:
diff changeset
3 (1) how to tell when to report a bug, and
Dave Love <fx@gnu.org>
parents:
diff changeset
4 (2) how to write a useful bug report and what information
Dave Love <fx@gnu.org>
parents:
diff changeset
5 it needs to have.
Dave Love <fx@gnu.org>
parents:
diff changeset
6
Dave Love <fx@gnu.org>
parents:
diff changeset
7 There are three ways to read the Bugs section.
Dave Love <fx@gnu.org>
parents:
diff changeset
8
Dave Love <fx@gnu.org>
parents:
diff changeset
9 (1) In a printed copy of the Emacs manual.
Dave Love <fx@gnu.org>
parents:
diff changeset
10 You can order one from the Free Software Foundation;
Dave Love <fx@gnu.org>
parents:
diff changeset
11 see the file etc/ORDERS. But if you don't have a copy on
Dave Love <fx@gnu.org>
parents:
diff changeset
12 hand and you think you have found a bug, you shouldn't wait
Dave Love <fx@gnu.org>
parents:
diff changeset
13 to get a printed manual; you should read the section right away
Dave Love <fx@gnu.org>
parents:
diff changeset
14 as described below.
Dave Love <fx@gnu.org>
parents:
diff changeset
15
Dave Love <fx@gnu.org>
parents:
diff changeset
16 (2) With Info. Start Emacs, do C-h i to enter Info,
Dave Love <fx@gnu.org>
parents:
diff changeset
17 then m Emacs RET to get to the Emacs manual, then m Bugs RET
Dave Love <fx@gnu.org>
parents:
diff changeset
18 to get to the section on bugs. Or use standalone Info in
Dave Love <fx@gnu.org>
parents:
diff changeset
19 a like manner. (Standalone Info is part of the Texinfo distribution,
Dave Love <fx@gnu.org>
parents:
diff changeset
20 not part of the Emacs distribution.)
Dave Love <fx@gnu.org>
parents:
diff changeset
21
Dave Love <fx@gnu.org>
parents:
diff changeset
22 (3) By hand. Do
Dave Love <fx@gnu.org>
parents:
diff changeset
23 cat info/emacs* | more "+/^File: emacs, Node: Bugs,"
Dave Love <fx@gnu.org>
parents:
diff changeset
24
34822
af68d12218d0 *** empty log message ***
Dave Love <fx@gnu.org>
parents: 25856
diff changeset
25 Please first check the file etc/PROBLEMS (e.g. with C-h P in Emacs) to
af68d12218d0 *** empty log message ***
Dave Love <fx@gnu.org>
parents: 25856
diff changeset
26 make sure it isn't a known issue.