procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Explain how to debug emacsclient lisp errors

Browse source 
* doc/lispref/debugging.texi (Error Debugging): Mention that
debug-on-signal is useful for getting backtraces from
emacsclient (Bug#24616).
This commit is contained in:
Noam Postavsky 2016-10-22 11:52:14 -04:00
parent 9da53e2d35
commit b2ba630739
1 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
doc/lispref/debugging.texi
View file

@ -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 must still fulfill the criteria specified by @code{debug-on-error} and
@code{debug-ignored-errors}.) @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 @strong{Warning:} Setting this variable to non-@code{nil} may have
annoying effects. Various parts of Emacs catch errors in the normal annoying effects. Various parts of Emacs catch errors in the normal
course of affairs, and you may not even realize that errors happen course of affairs, and you may not even realize that errors happen