| 309 | | Try evaluating (x-synchronize t). That puts Emacs into synchronous |
|---|
| 310 | | mode, where each Xlib call checks for errors before it returns. This |
|---|
| 311 | | mode is much slower, but when you get an error, you will see exactly |
|---|
| 312 | | which call really caused the error. |
|---|
| | 309 | The X server normally reports protocol errors asynchronously, |
|---|
| | 310 | so you find out about them long after the primitive which caused |
|---|
| | 311 | the error has returned. |
|---|
| | 312 | |
|---|
| | 313 | To get clear information about the cause of an error, try evaluating |
|---|
| | 314 | (x-synchronize t). That puts Emacs into synchronous mode, where each |
|---|
| | 315 | Xlib call checks for errors before it returns. This mode is much |
|---|
| | 316 | slower, but when you get an error, you will see exactly which call |
|---|
| | 317 | really caused the error. |
|---|
