From: Eli Zaretskii Date: Sat, 4 Aug 2001 12:39:30 +0000 (+0000) Subject: (Lossage, Bugs): Mention etc/PROBLEMS and the Bugs section of the FAQ. X-Git-Tag: emacs-pretest-21.0.105~290 X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=9e25ea70c151aa34857160781103f43abb9c1a79;p=emacs.git (Lossage, Bugs): Mention etc/PROBLEMS and the Bugs section of the FAQ. Suggested by David Kastrup . --- diff --git a/man/trouble.texi b/man/trouble.texi index a695afa409d..877cdcc7d24 100644 --- a/man/trouble.texi +++ b/man/trouble.texi @@ -121,7 +121,10 @@ about the undo facility. @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 @@ they are bugs and want to fix them. 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.