view BUGS @ 45132:c26266baaba5

(filesets-browse-dir-function): Renamed from ...-fn. (filesets-open-file-function, filesets-save-buffer-function): Likewise. (filesets-tree-max-level): Doc fix. (filesets-commands, filesets-external-viewers) (filesets-ingroup-patterns): Mark as risky. (filesets-cache-hostname-flag): Doc fix. (filesets-menu-cache-file): Doc fix. Mark as risky. (filesets-menu-before, filesets-menu-path, filesets-menu-in-menu): Don't defcustom them if running in Emacs.
author Richard M. Stallman <rms@gnu.org>
date Sun, 05 May 2002 01:55:25 +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.