From 9db97b49cd25d1034e4b609bebbac320ad0d3117 Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Fri, 8 Jun 2018 18:22:50 +0300 Subject: ; * etc/DEBUG: Add information about debugging libXft problems. --- etc/DEBUG | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) (limited to 'etc/DEBUG') 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: -- cgit v1.2.1