Mercurial > emacs
view BUGS @ 53442:01eff098e535
* toolbar/gud-next.pbm, toolbar/gud-next.xpm
* toolbar/gud-nexti.pbm, toolbar/gud-nexti.xpm
* toolbar/gud-step.pbm, toolbar/gud-step.xpm
* toolbar/gud-stepi.pbm, toolbar/gud-stepi.xpm: Renamed to
gud-n.*, gud-ni.*, gud-s.*, and gud-si.*, respectively, to avoid
file-name clashes on 8+3 filesystems.
author | Eli Zaretskii <eliz@is.elta.co.il> |
---|---|
date | Tue, 30 Dec 2003 08:49:27 +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.