unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Pogonyshev <pogonyshev@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Backtrace printing in batch mode ignores all customizations
Date: Sat, 21 Dec 2019 11:22:13 +0200	[thread overview]
Message-ID: <83tv5uyqwq.fsf@gnu.org> (raw)
In-Reply-To: <CAG7BpaqeM5xoHxb=E3eFMUS6kdNLBb6W3Ge1sFjQhVgUf+nJqQ@mail.gmail.com> (message from Paul Pogonyshev on Mon, 16 Dec 2019 23:34:42 +0100)

> From: Paul Pogonyshev <pogonyshev@gmail.com>
> Date: Mon, 16 Dec 2019 23:34:42 +0100
> 
> +   ((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.

Can you please elaborate about the debug/backtrace customizations you
did, which are bypassed due to this code?  What are those
customizations supposed to do?



  reply	other threads:[~2019-12-21  9:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-16 22:34 Backtrace printing in batch mode ignores all customizations Paul Pogonyshev
2019-12-21  9:22 ` Eli Zaretskii [this message]
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=83tv5uyqwq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=pogonyshev@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 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).