This file looks large and may slow your browser down if we attempt
to syntax highlight it, so we are showing it without any
pretty colors.
Highlight
it anyway.
| 1 |
If you think you may have found a bug in GNU Emacs, please |
| 2 |
read the Bugs section of the Emacs manual for advice on |
| 3 |
(1) how to tell when to report a bug, and |
| 4 |
(2) how to write a useful bug report and what information |
| 5 |
it needs to have. |
| 6 |
|
| 7 |
There are three ways to read the Bugs section. |
| 8 |
|
| 9 |
(1) In a printed copy of the Emacs manual. |
| 10 |
You can order one from the Free Software Foundation; |
| 11 |
see the file etc/ORDERS. But if you don't have a copy on |
| 12 |
hand and you think you have found a bug, you shouldn't wait |
| 13 |
to get a printed manual; you should read the section right away |
| 14 |
as described below. |
| 15 |
|
| 16 |
(2) With Info. Start Emacs, do C-h i to enter Info, |
| 17 |
then m Emacs RET to get to the Emacs manual, then m Bugs RET |
| 18 |
to get to the section on bugs. Or use standalone Info in |
| 19 |
a like manner. (Standalone Info is part of the Texinfo distribution, |
| 20 |
not part of the Emacs distribution.) |
| 21 |
|
| 22 |
(3) By hand. Do |
| 23 |
cat info/emacs* | more "+/^File: emacs, Node: Bugs," |
| 24 |
|
| 25 |
Please first check the file etc/PROBLEMS (e.g. with C-h C-p in Emacs) to |
| 26 |
make sure it isn't a known issue. |