GNU bug report logs - #24616
26.0.50; No backtrace when emacsclient --eval fails

Previous Next

Full log

Message #32 received at 24616 <at> debbugs.gnu.org (full text, mbox):

From: npostavs <at> users.sourceforge.net
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 24616 <at> debbugs.gnu.org, clement.pit <at> gmail.com
Subject: Re: bug#24616: 26.0.50; No backtrace when emacsclient --eval fails
Date: Sat, 22 Oct 2016 12:08:47 -0400

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: npostavs <at> users.sourceforge.net
>> Cc: 24616 <at> debbugs.gnu.org,  clement.pit <at> gmail.com
>> Date: Sat, 22 Oct 2016 11:35:49 -0400
>> 
>> Something like this?
>> 
>> diff --git i/doc/lispref/debugging.texi w/doc/lispref/debugging.texi
>> index c88a2fa..bb3ced4 100644
>> --- i/doc/lispref/debugging.texi
>> +++ w/doc/lispref/debugging.texi
>> @@ -152,6 +152,11 @@ Error Debugging
>>  must still fulfill the criteria specified by @code{debug-on-error} and
>>  @code{debug-ignored-errors}.)
>>  
>> +For example, setting this variable is useful to get a backtrace from
>> +code evaluated by emacsclient.  If elisp code evaluated by emacsclient
>> +signals an error while this variable is non-@code{nil}, the backtrace
>> +will popup in the running Emacs.
>> +
>
> Yes, but please mention "--eval", and add an index entry so that this
> text would be easier to locate.  Something like this:
>
>   @cindex emacsclient, getting a backtrace
>   @cindex backtrace from emacsclient's @option{--eval}
>
> Also, a nit: I don't think we use "elisp" in the manual, we say
> "Lisp" instead.
>
> Thanks.

Fixed and pushed as b2ba6307 "Explain how to debug emacsclient lisp
errors".

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.