From: Paul Pogonyshev <pogonyshev@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Backtrace printing in batch mode ignores all customizations
Date: Mon, 16 Dec 2019 23:34:42 +0100 [thread overview]
Message-ID: <CAG7BpaqeM5xoHxb=E3eFMUS6kdNLBb6W3Ge1sFjQhVgUf+nJqQ@mail.gmail.com> (raw)
Apparently it is because of this commit:
7228488effa78dcb75284cb6d247b24804e0e7f5
Author: Stefan Monnier <monnier@iro.umontreal.ca>
AuthorDate: 2018-04-02 00:23:20 -0400
[...]
* lisp/emacs-lisp/debug.el (debug): Don't hang upon error in initial-frame.
[...]
+ ((and (eq t (framep (selected-frame)))
+ (equal "initial_terminal" (terminal-name)))
+ ;; We're in the initial-frame (where `message' just outputs to stdout) so
+ ;; there's no tty or GUI frame to display the backtrace and interact with
+ ;; it: just dump a backtrace to stdout.
+ ;; This happens for example while handling an error in code from
+ ;; early-init.el with --debug-init.
+ (message "Error: %S" args)
[...]
The condition seems to always be true when `noninteractive' is t. Is
this intentional? It appears to mean that all debug/backtrace
customizations in batch mode are meaningless, since debugger just goes
the "failsafe" route and prints backtrace with simple `message' calls
now.
Please CC me, I'm not subscribed.
Paul
next reply other threads:[~2019-12-16 22:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 22:34 Paul Pogonyshev [this message]
2019-12-21 9:22 ` Backtrace printing in batch mode ignores all customizations Eli Zaretskii
2019-12-21 17:07 ` Paul Pogonyshev
2020-01-04 22:44 ` Stefan Monnier
2020-01-04 23:12 ` Paul Pogonyshev
2020-01-04 23:31 ` Stefan Monnier
2020-01-12 15:49 ` Paul Pogonyshev
2020-01-13 19:23 ` Stefan Monnier
2020-01-14 15:41 ` Eli Zaretskii
2020-01-14 17:51 ` Paul Pogonyshev
2020-01-14 19:57 ` Eli Zaretskii
2020-01-14 20:30 ` Stefan Monnier
2020-01-15 15:58 ` Eli Zaretskii
2020-01-15 17:34 ` Stefan Monnier
2020-01-15 17:54 ` Eli Zaretskii
2020-01-15 18:59 ` Stefan Monnier
2020-01-25 14:32 ` Paul Pogonyshev
2020-01-28 2:52 ` Richard Stallman
2020-01-27 3:55 ` Stefan Monnier
2020-01-29 11:09 ` Paul Pogonyshev
2020-01-31 14:14 ` Eli Zaretskii
2020-01-31 18:10 ` Paul Pogonyshev
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAG7BpaqeM5xoHxb=E3eFMUS6kdNLBb6W3Ge1sFjQhVgUf+nJqQ@mail.gmail.com' \
--to=pogonyshev@gmail.com \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).