view BUGS @ 40464:f1e32a9da9a8

(edebug-window-live-p): Always alias to window-live-p. (edebug-set-conditional-breakpoint): Unconditionally use the former Emacs >=19 definition. (edebug-mark): Define unconditionally. (edebug-eval-expression): Always call read-from-minibuffer and specify history list. (edebug-lemacs-specific): Override emacs-mark, edebug-window-live-p, edebug-set-conditional-breakpoint. (edebug-emacs-version-specific): Function deleted; do the job at top level. (edebug-emacs-19-specific): Function deleted, this is the default.
author Richard M. Stallman <rms@gnu.org>
date Tue, 30 Oct 2001 00:21:34 +0000
parents af68d12218d0
children 8ce686bd7f4f
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 P in Emacs) to
make sure it isn't a known issue.