diff options
| author | Richard M. Stallman <rms@gnu.org> | 2007-03-26 03:28:55 +0000 |
|---|---|---|
| committer | Richard M. Stallman <rms@gnu.org> | 2007-03-26 03:28:55 +0000 |
| commit | 404cadcd95cadf8bf37c057a2dbb94c8ba613d64 (patch) | |
| tree | e322479859192597ec90dd4b535a829cb7efa3ea | |
| parent | 3f9ee87935a97dd4fac54975267cd520aa342b96 (diff) | |
| download | emacs-404cadcd95cadf8bf37c057a2dbb94c8ba613d64.tar.gz | |
Explain reason for X protocol error recommendations.
| -rw-r--r-- | etc/DEBUG | 13 |
1 files changed, 9 insertions, 4 deletions
diff --git a/etc/DEBUG b/etc/DEBUG index ad59d48b3ca..97e1f015a05 100644 --- a/etc/DEBUG +++ b/etc/DEBUG @@ -306,10 +306,15 @@ debugger, type "gdb temacs", then start it with `r -batch -l loadup'. ** 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: |