diff options
author | Eli Zaretskii <eliz@gnu.org> | 2018-06-08 18:22:50 +0300 |
---|---|---|
committer | Eli Zaretskii <eliz@gnu.org> | 2018-06-08 18:22:50 +0300 |
commit | 9db97b49cd25d1034e4b609bebbac320ad0d3117 (patch) | |
tree | 0b6254c0f966b36abc33efba5d69e15b9336aeab /etc/DEBUG | |
parent | 0214ffbe60fe0676219125a93b6521625ca7c879 (diff) | |
download | emacs-9db97b49cd25d1034e4b609bebbac320ad0d3117.tar.gz |
; * etc/DEBUG: Add information about debugging libXft problems.
Diffstat (limited to 'etc/DEBUG')
-rw-r--r-- | etc/DEBUG | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/etc/DEBUG b/etc/DEBUG index bd6ea74fa72..50417af5766 100644 --- a/etc/DEBUG +++ b/etc/DEBUG @@ -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 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. +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 synchronous mode. To track down those bugs, we suggest the following procedure: |