[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#24616: 26.0.50; No backtrace when emacsclient --eval fails
From: |
npostavs |
Subject: |
bug#24616: 26.0.50; No backtrace when emacsclient --eval fails |
Date: |
Sat, 22 Oct 2016 12:08:47 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Eli Zaretskii <eliz@gnu.org> writes:
>> From: npostavs@users.sourceforge.net
>> Cc: 24616@debbugs.gnu.org, clement.pit@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".
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Philipp Stephani, 2016/10/04
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Eli Zaretskii, 2016/10/04
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Noam Postavsky, 2016/10/04
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Clément Pit--Claudel, 2016/10/04
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Noam Postavsky, 2016/10/04
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Clément Pit--Claudel, 2016/10/04
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Eli Zaretskii, 2016/10/05
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, npostavs, 2016/10/22
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Eli Zaretskii, 2016/10/22
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails,
npostavs <=
bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Live System User, 2016/10/23