aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--etc/DEBUG10
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
647protocol errors from subsequent invocations of emacsclient in a GUI 647protocol errors from subsequent invocations of emacsclient in a GUI
648frame. In that case calling the initial Emacs via 648frame. In that case calling the initial Emacs via
649 649
650emacs -nw --eval '(setq x-command-line-resources "emacs.synchronous: true")' 650 emacs -nw --eval '(setq x-command-line-resources "emacs.synchronous: true")'
651 651
652should give more reliable results. 652should give more reliable results.
653 653
654For X protocol errors related to displaying unusual characters or to
655font-related customizations, try invoking Emacs like this:
656
657 XFT_DEBUG=16 emacs -xrm "emacs.synchronous: true"
658
659This should produce information from the libXft library which could
660give useful hints regarding font-related problems in that library.
661
654Some bugs related to the X protocol disappear when Emacs runs in a 662Some bugs related to the X protocol disappear when Emacs runs in a
655synchronous mode. To track down those bugs, we suggest the following 663synchronous mode. To track down those bugs, we suggest the following
656procedure: 664procedure: