From b2ba630739cf12db939cdcfe9cd19b6a7fdfbf97 Mon Sep 17 00:00:00 2001 From: Noam Postavsky Date: Sat, 22 Oct 2016 11:52:14 -0400 Subject: [PATCH] Explain how to debug emacsclient lisp errors * doc/lispref/debugging.texi (Error Debugging): Mention that debug-on-signal is useful for getting backtraces from emacsclient (Bug#24616). --- doc/lispref/debugging.texi | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi index c88a2fa60e0..371934377a8 100644 --- a/doc/lispref/debugging.texi +++ b/doc/lispref/debugging.texi @@ -152,6 +152,13 @@ presence of @code{condition-case}. (To invoke the debugger, the error must still fulfill the criteria specified by @code{debug-on-error} and @code{debug-ignored-errors}.) +@cindex emacsclient, getting a backtrace +@cindex backtrace from emacsclient's @option{--eval} +For example, setting this variable is useful to get a backtrace from +code evaluated by emacsclient's @option{--eval} option. If Lisp code +evaluated by emacsclient signals an error while this variable is +non-@code{nil}, the backtrace will popup in the running Emacs. + @strong{Warning:} Setting this variable to non-@code{nil} may have annoying effects. Various parts of Emacs catch errors in the normal course of affairs, and you may not even realize that errors happen -- 2.39.5