From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 44942@debbugs.gnu.org
Subject: bug#44942: 28.0.50; Emacs should print a backtrace on uncaught errors in batch mode
Date: Mon, 7 Dec 2020 12:07:48 +0100 [thread overview]
Message-ID: <CAArVCkSC=+gm=QXHduWKKLCn7A=j8aNXsxOFy7iS8coYj8csDQ@mail.gmail.com> (raw)
In-Reply-To: <1DC46C7A-D0A8-4B92-84FE-3ABA2F6A6624@gnu.org>
Am Mo., 7. Dez. 2020 um 11:42 Uhr schrieb Eli Zaretskii <eliz@gnu.org>:
>
> On December 7, 2020 12:29:16 PM GMT+02:00, Philipp Stephani <p.stephani2@gmail.com> wrote:
> > Am So., 6. Dez. 2020 um 18:00 Uhr schrieb Eli Zaretskii
> > <eliz@gnu.org>:
> > >
> > > > From: Philipp Stephani <p.stephani2@gmail.com>
> > > > Date: Sun, 6 Dec 2020 17:50:17 +0100
> > > >
> > > > Am So., 29. Nov. 2020 um 16:27 Uhr schrieb Philipp Stephani
> > > > <p.stephani2@gmail.com>:
> > > > >
> > > > Pushed to master as commit 40e11743ca.
> > >
> > > This is an incompatible change.
> >
> > Is it? In other words, do we guarantee that no stack trace is being
> > printed if debug-on-error is nil? I'd say that parsing error messages
> > is brittle anyway, and we're not obliged to provide stable output
>
> The behavior did change. Since Emacs doesn't have a formal spec its long-time behavior is a de-facto standard we should strive hard not to break. As Stefan just pointed out, this change already broke 2 tests if we need any proof.
>
> > > Is there a way to get back previous
> > > behavior? If so, please mention that in NEWS; if not, let's please
> > > provide a way to get back the old behavior.
> >
> > I'd be OK adding a variable for this, but on the other hand I'm not
> > really convinced that this is really a breaking change (see above).
>
> Yes, we do need to be able to get back the old bdhavior.
Fair enough, I've added a new boolean variable for this.
next prev parent reply other threads:[~2020-12-07 11:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 10:47 bug#44942: 28.0.50; Emacs should print a backtrace on uncaught errors in batch mode Philipp Stephani
2020-11-29 15:27 ` Philipp Stephani
2020-12-06 16:50 ` Philipp Stephani
2020-12-06 16:59 ` Eli Zaretskii
2020-12-07 10:29 ` Philipp Stephani
2020-12-07 10:42 ` Eli Zaretskii
2020-12-07 11:07 ` Philipp Stephani [this message]
2020-12-07 15:45 ` Eli Zaretskii
2020-12-07 15:07 ` Mattias Engdegård
2020-12-07 15:29 ` 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='CAArVCkSC=+gm=QXHduWKKLCn7A=j8aNXsxOFy7iS8coYj8csDQ@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=44942@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.