Backtrace printing in batch mode ignores all customizations

[Paul Pogonyshev]

Apparently it is because of this commit:

7228488effa78dcb75284cb6d247b24804e0e7f5
Author:     Stefan Monnier <address@hidden>
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