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

; * etc/DEBUG: Add information about debugging libXft problems.

Browse source
This commit is contained in:
Eli Zaretskii 2018-06-08 18:22:50 +03:00
parent 0214ffbe60
commit 9db97b49cd
1 changed files with 9 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

10
etc/DEBUG
View file

@ -647,10 +647,18 @@ process invoked with the -nw option a server and want to trace X
protocol errors from subsequent invocations of emacsclient in a GUI protocol errors from subsequent invocations of emacsclient in a GUI
frame. In that case calling the initial Emacs via frame. In that case calling the initial Emacs via
emacs -nw --eval '(setq x-command-line-resources "emacs.synchronous: true")' emacs -nw --eval '(setq x-command-line-resources "emacs.synchronous: true")'
should give more reliable results. should give more reliable results.
For X protocol errors related to displaying unusual characters or to
font-related customizations, try invoking Emacs like this:
XFT_DEBUG=16 emacs -xrm "emacs.synchronous: true"
This should produce information from the libXft library which could
give useful hints regarding font-related problems in that library.
Some bugs related to the X protocol disappear when Emacs runs in a Some bugs related to the X protocol disappear when Emacs runs in a
synchronous mode. To track down those bugs, we suggest the following synchronous mode. To track down those bugs, we suggest the following
procedure: procedure: