From e3b85775252adbe3135580df321cbd69eb2f2bf1 Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Thu, 25 Aug 2022 22:07:04 +0300 Subject: [PATCH] ; * etc/DEBUG: Fix wording of "X protocol errors" section. --- etc/DEBUG | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/etc/DEBUG b/etc/DEBUG index dd33b42f19a..5d99c313f93 100644 --- a/etc/DEBUG +++ b/etc/DEBUG @@ -661,10 +661,10 @@ 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 +Note that the -xrm option may have no effect when you start a server +in an Emacs session invoked with the -nw command-line option, and want +to trace X protocol errors from GUI frames created by subsequent +invocations of emacsclient. In that case starting Emacs via emacs -nw --eval '(setq x-command-line-resources "emacs.synchronous: true")' -- 2.39.2