procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

; Drop note about tracing X protocol errors from a TTY based server

Browse source 
* etc/DEBUG: Drop note about how to trace X protocol errors when
a GUI client connects to a server running from a text terminal.
This commit is contained in:
Martin Rudalics 2017-09-03 19:27:52 +02:00
parent 673e6d35ac
commit 96c23a19fd
1 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
etc/DEBUG
View file

@ -622,6 +622,15 @@ Setting a breakpoint in the function 'x_error_quitter' and looking at
the backtrace when Emacs stops inside that function will show what
code causes the X protocol errors.
Note that the -xrm option may have no effect when you make an Emacs
process invoked with the -nw option a server and want to trace X
protocol errors from subsequent invocations of emacsclient in a GUI
frame. In that case calling the initial Emacs via
emacs -nw --eval '(setq x-command-line-resources "emacs.synchronous: true")'
should give more reliable results.
Some bugs related to the X protocol disappear when Emacs runs in a
synchronous mode. To track down those bugs, we suggest the following
procedure: