view BUGS @ 81414:92493f24adc9

Merge from emacs--rel--22 Patches applied: * emacs--rel--22 (patch 43-44) - Update from CVS - Merge from gnus--rel--5.10 * gnus--rel--5.10 (patch 229) - Merge from emacs--devo--0, emacs--rel--22 2007-06-11 Stefan Monnier <monnier@iro.umontreal.ca> * lisp/font-lock.el (font-lock-add-keywords): In case font-lock was only half-activated, forcefully activate it completely. 2007-06-11 Richard Stallman <rms@gnu.org> * lisp/cus-edit.el (custom-variable-type): Doc fix. Revision: emacs@sv.gnu.org/emacs--devo--0--patch-797
author Miles Bader <miles@gnu.org>
date Thu, 14 Jun 2007 09:59:49 +0000
parents 8ce686bd7f4f
children fb8bf24d2eb9
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,"

Please first check the file etc/PROBLEMS (e.g. with C-h C-e in Emacs) to
make sure it isn't a known issue.