From: Philipp Stephani <p.stephani2@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Stefan Kangas <stefankangas@gmail.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: master 40e1174: Print a backtrace on unhandled errors in batch mode (Bug#44942).
Date: Mon, 7 Dec 2020 16:27:19 +0100 [thread overview]
Message-ID: <CAArVCkT-RFYSY3DhQdREnT=rzArJ8VdJzxnf_+ikfMEZ9kZ4Aw@mail.gmail.com> (raw)
In-Reply-To: <jwv1rg1abvq.fsf-monnier+emacs@gnu.org>
Am Mo., 7. Dez. 2020 um 16:13 Uhr schrieb Stefan Monnier
<monnier@iro.umontreal.ca>:
>
> > Outputting a backtrace in -batch mode is good, but I think having it on
> > by default will lead to too many regressions.
>
> I think it makes sense to link it to `debug-on-error` (since we can't
> really "debug" in batch mode, printing the backtrace is about as good
> of an approximation as you can get).
>
No, it should definitely not linked to debug-on-error. debug-on-error
doesn't really work: it changes the meaning of important macros such
as condition-case-unless-debug or with-demoted-errors. debug-on-error
only makes sense in interactive mode, where the user is actually able
to debug such "demoted" errors.
next prev parent reply other threads:[~2020-12-07 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201206164942.28653.54315@vcs0.savannah.gnu.org>
[not found] ` <20201206164944.2472A205D7@vcs0.savannah.gnu.org>
2020-12-07 10:11 ` master 40e1174: Print a backtrace on unhandled errors in batch mode (Bug#44942) Stefan Kangas
2020-12-07 11:08 ` Philipp Stephani
2020-12-07 11:30 ` Lars Ingebrigtsen
2020-12-07 15:13 ` Stefan Monnier
2020-12-07 15:27 ` Philipp Stephani [this message]
2020-12-07 15:28 ` Philipp Stephani
2020-12-07 15:42 ` Lars Ingebrigtsen
2020-12-07 15:48 ` Eli Zaretskii
2020-12-12 14:36 ` Philipp Stephani
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='CAArVCkT-RFYSY3DhQdREnT=rzArJ8VdJzxnf_+ikfMEZ9kZ4Aw@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@gmail.com \
/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.