[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: master 40e1174: Print a backtrace on unhandled errors in batch mode
From: |
Philipp Stephani |
Subject: |
Re: master 40e1174: Print a backtrace on unhandled errors in batch mode (Bug#44942). |
Date: |
Mon, 7 Dec 2020 16:27:19 +0100 |
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.