Mercurial > emacs
changeset 76739:e4f81c51941e
Explain reason for X protocol error recommendations.
| author | Richard M. Stallman <rms@gnu.org> |
|---|---|
| date | Mon, 26 Mar 2007 03:28:55 +0000 |
| parents | c39f6a4ef598 |
| children | 212e8c8f31b0 |
| files | etc/DEBUG |
| diffstat | 1 files changed, 9 insertions(+), 4 deletions(-) [+] |
line wrap: on
line diff
--- 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: