diff options
| author | Eli Zaretskii | 2001-03-23 12:38:16 +0000 |
|---|---|---|
| committer | Eli Zaretskii | 2001-03-23 12:38:16 +0000 |
| commit | ec4054f004dca3f84c30e60646ec5bd71dae9c56 (patch) | |
| tree | 2513d184f1e9f91513c56ff0c5f973e29fdcbcbd | |
| parent | 091f887891422b7fc5e769b62c76cc6600ccc7b1 (diff) | |
| download | emacs-ec4054f004dca3f84c30e60646ec5bd71dae9c56.tar.gz emacs-ec4054f004dca3f84c30e60646ec5bd71dae9c56.zip | |
Document the use of -xrm to start EMacs in synchronous mode.
| -rw-r--r-- | etc/DEBUG | 9 |
1 files changed, 9 insertions, 0 deletions
| @@ -249,6 +249,15 @@ mode, where each Xlib call checks for errors before it returns. This | |||
| 249 | mode is much slower, but when you get an error, you will see exactly | 249 | mode is much slower, but when you get an error, you will see exactly |
| 250 | which call really caused the error. | 250 | which call really caused the error. |
| 251 | 251 | ||
| 252 | You can start Emacs in a synchronous mode by invoking it with the -xrm | ||
| 253 | option, like this: | ||
| 254 | |||
| 255 | emacs -rm "emacs.synchronous: true" | ||
| 256 | |||
| 257 | Setting a breakpoint in the function `x_error_quitter' and looking at | ||
| 258 | the backtrace when Emacs stops inside that function will show what | ||
| 259 | code causes the X protocol errors. | ||
| 260 | |||
| 252 | ** If the symptom of the bug is that Emacs fails to respond | 261 | ** If the symptom of the bug is that Emacs fails to respond |
| 253 | 262 | ||
| 254 | Don't assume Emacs is `hung'--it may instead be in an infinite loop. | 263 | Don't assume Emacs is `hung'--it may instead be in an infinite loop. |