Re: Backtrace printing in batch mode ignores all customizations

[Stefan Monnier]

> noninteractive)" condition. In the patch I didn't try to unify your
> "failsafe" mode with non-interactive use, since I don't really know
> what you wrote the commit for.

The commit was specifically prompted by the case mentioned in the comment:

      ;; This happens for example while handling an error in code from
      ;; early-init.el with --debug-init.

I can't remember the exact previous behavior, but it was not right (you
got neither a good *backtrace* because the GUI wasn't up, nor a clean
stacktrace on stdout/stderr).


        Stefan