(Lossage, Bugs): Mention etc/PROBLEMS and the Bugs section of the FAQ.

Suggested by David Kastrup <David.Kastrup@neuroinformatik.ruhr-uni-bochum.de>.

diff --git a/man/trouble.texi b/man/trouble.texi
index a695afa409dbae7fc6771a1586d555916929a812..877cdcc7d2437b312b1602f51a46c40add6e3c09 100644 (file)
--- 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.