# HG changeset patch
# User Richard M. Stallman <rms@gnu.org>
# Date 1174879735 0
# Node ID e4f81c51941ed226a1aba215400d519c885b84ec
# Parent  c39f6a4ef598686d4ddff2f701867c688176bade
Explain reason for X protocol error recommendations.

diff -r c39f6a4ef598 -r e4f81c51941e etc/DEBUG
--- a/etc/DEBUG	Mon Mar 26 02:29:08 2007 +0000
+++ b/etc/DEBUG	Mon Mar 26 03:28:55 2007 +0000
@@ -306,10 +306,15 @@
 
 ** If you encounter X protocol errors
 
-Try evaluating (x-synchronize t).  That puts Emacs into synchronous
-mode, where each Xlib call checks for errors before it returns.  This
-mode is much slower, but when you get an error, you will see exactly
-which call really caused the error.
+The X server normally reports protocol errors asynchronously,
+so you find out about them long after the primitive which caused
+the error has returned.
+
+To get clear information about the cause of an error, try evaluating
+(x-synchronize t).  That puts Emacs into synchronous mode, where each
+Xlib call checks for errors before it returns.  This mode is much
+slower, but when you get an error, you will see exactly which call
+really caused the error.
 
 You can start Emacs in a synchronous mode by invoking it with the -xrm
 option, like this: