From: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>
Subject: stack-trace-on-error vs. debug-on-error.
Date: Fri, 04 Mar 2005 10:40:59 +0100 [thread overview]
Message-ID: <87ll93lpec.fsf@xs4all.nl> (raw)
Does anyone know the difference between stack-trace-on-error and
debug-on-error?
,----[ C-h v stack-trace-on-error RET ]
| stack-trace-on-error's value is nil
|
| *Non-nil means errors display a backtrace buffer.
| More precisely, this happens for any error that is handled
| by the editor command loop.
| If the value is a list, an error only means to display a backtrace
| if one of its condition symbols appears in the list.
|
| You can customize this variable.
|
| Defined in `C source code'.
`----
,----[ C-h v debug-on-error RET ]
| debug-on-error's value is nil
|
| *Non-nil means enter debugger if an error is signaled.
| Does not apply to errors handled by `condition-case' or those
| matched by `debug-ignored-errors'.
| If the value is a list, an error only means to enter the debugger
| if one of its condition symbols appears in the list.
| When you evaluate an expression interactively, this variable
| is temporarily non-nil if `eval-expression-debug-on-error' is non-nil.
| See also variable `debug-on-quit'.
|
| You can customize this variable.
|
| Defined in `C source code'.
`----
On first inspection they seem to do exactly the same.
stack-trace-on-error is not documented in Emacs manual or the Lisp
manual. Would it be safe to make it an alias of debug-on-error and
mark it as obsolete?
Lute.
next reply other threads:[~2005-03-04 9:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 9:40 Lute Kamstra [this message]
2005-03-04 10:04 ` stack-trace-on-error vs. debug-on-error Lute Kamstra
2005-03-04 11:09 ` Lute Kamstra
2005-03-05 16:59 ` Richard Stallman
2005-03-07 1:42 ` Chris Smith
-- strict thread matches above, loose matches on Subject: below --
2005-03-04 13:47 drkm
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=87ll93lpec.fsf@xs4all.nl \
--to=lute.kamstra.lists@xs4all.nl \
/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.