Re: Backtrace printing in batch mode ignores all customizations

[Eli Zaretskii]

> From: Paul Pogonyshev <address@hidden>
> 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?