[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:28:39 +0100 |
Am Mo., 7. Dez. 2020 um 12:30 Uhr schrieb Lars Ingebrigtsen <larsi@gnus.org>:
>
> Stefan Kangas <stefankangas@gmail.com> writes:
>
> > p.stephani2@gmail.com (Philipp Stephani) writes:
> >
> >> branch: master
> >> commit 40e11743ca3803bdc2c6c612f35ab695efb3eb8b
> >> Author: Philipp Stephani <phst@google.com>
> >> Commit: Philipp Stephani <phst@google.com>
> >>
> >> Print a backtrace on unhandled errors in batch mode (Bug#44942).
> >
> > This causes some test failures:
> >
> > 1 files did not finish:
> > lisp/emacs-lisp/edebug-tests.log
> > 1 files contained unexpected results:
> > lisp/emacs-lisp/gv-tests.log
>
> I think it would be good if there was a command line switch for this
> (for instance, -backtrace).
>
> Outputting a backtrace in -batch mode is good, but I think having it on
> by default will lead to too many regressions.
>
I don't expect that. Parsing the debug output of programs is always
rather brittle, and I wouldn't expect users outside of Emacs itself to
rely on a specific output format.