Mercurial > emacs
changeset 38686:0d3019db87ac
(Lossage, Bugs): Mention etc/PROBLEMS and the Bugs section of the FAQ.
Suggested by David Kastrup <David.Kastrup@neuroinformatik.ruhr-uni-bochum.de>.
| author | Eli Zaretskii <eliz@gnu.org> |
|---|---|
| date | Sat, 04 Aug 2001 12:39:30 +0000 |
| parents | 3d0bec9036ac |
| children | 14401c0b4b44 |
| files | man/trouble.texi |
| diffstat | 1 files changed, 12 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/man/trouble.texi Sat Aug 04 12:15:32 2001 +0000 +++ b/man/trouble.texi Sat Aug 04 12:39:30 2001 +0000 @@ -121,7 +121,10 @@ @section Dealing with Emacs Trouble This section describes various conditions in which Emacs fails to work -normally, and how to recognize them and correct them. +normally, and how to recognize them and correct them. For a list of +additional problems you might encounter, see @ref{Bugs and problems, , +Bugs and problems, efaq, GNU Emacs FAQ}, and the file @file{etc/PROBLEMS} +in the Emacs distribution. @menu * DEL Gets Help:: What to do if @key{DEL} doesn't delete. @@ -420,6 +423,14 @@ To make it possible for us to fix a bug, you must report it. In order to do so effectively, you must know when and how to do it. + Before reporting a bug, it is a good idea to see if it is already +known. You can find the list of known problems in the file +@file{etc/PROBLEMS} in the Emacs distribution. Some additional +user-level problems can be found in @ref{Bugs and problems, , Bugs and +problems, efaq, GNU Emacs FAQ}. Looking up your problem in these two +documents might provide you with a solution or a work-around, or give +you additional information about related issues. + @menu * Criteria: Bug Criteria. Have you really found a bug? * Understanding Bug Reporting:: How to report a bug effectively.