view BUGS @ 85730:a1e136978a9a

(byte-compile-warnings): Document `not'. (byte-compile-warnings-safe-p): Handle `not'. (byte-compile-warning-enabled-p, byte-compile-disable-warning) (byte-compile-enable-warning): New functions. (byte-compile-eval-before-compile) (byte-compile-file-form-require): Use byte-compile-disable-warning. (byte-compile-close-variables): Locally bind byte-compile-warnings, but do not modify it. (byte-compile-eval, byte-compile-obsolete) (byte-compile-warn-about-unresolved-functions) (byte-compile-file-form-defvar) (byte-compile-file-form-custom-declare-variable) (byte-compile-file-form-require) (byte-compile-file-form-defmumble, byte-compile-lambda) (byte-compile-form, byte-compile-normal-call) (byte-compile-variable-ref, byte-compile-defvar) (byte-compile-make-variable-buffer-local): Use byte-compile-warning-enabled-p.
author Glenn Morris <rgm@gnu.org>
date Sun, 28 Oct 2007 23:52:50 +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.