From: Eli Zaretskii <eliz@gnu.org>
To: npostavs@users.sourceforge.net
Cc: 24616@debbugs.gnu.org, clement.pit@gmail.com
Subject: bug#24616: 26.0.50; No backtrace when emacsclient --eval fails
Date: Sat, 22 Oct 2016 18:52:54 +0300 [thread overview]
Message-ID: <83shropei1.fsf@gnu.org> (raw)
In-Reply-To: <877f90tmzu.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net)
> 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.
next prev parent reply other threads:[~2016-10-22 15:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 16:30 bug#24616: 26.0.50; No backtrace when emacsclient --eval fails Philipp Stephani
2016-10-04 17:15 ` Eli Zaretskii
2016-10-04 20:52 ` Noam Postavsky
2016-10-04 22:28 ` Clément Pit--Claudel
2016-10-04 23:50 ` Noam Postavsky
2016-10-05 0:02 ` Clément Pit--Claudel
2016-10-05 6:41 ` Eli Zaretskii
2016-10-22 15:35 ` npostavs
2016-10-22 15:52 ` Eli Zaretskii [this message]
2016-10-22 16:08 ` npostavs
2019-11-02 1:09 ` Stefan Kangas
2019-11-18 21:05 ` Philipp Stephani
2019-11-19 14:31 ` Stefan Kangas
2016-10-24 0:51 ` Live System User
2016-10-26 1:46 ` Noam Postavsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83shropei1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24616@debbugs.gnu.org \
--cc=clement.pit@gmail.com \
--cc=npostavs@users.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.