From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Paul Pogonyshev Newsgroups: gmane.emacs.devel Subject: Backtrace printing in batch mode ignores all customizations Date: Mon, 16 Dec 2019 23:34:42 +0100 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="82705"; mail-complaints-to="usenet@blaine.gmane.org" To: Emacs developers Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 16 23:35:27 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1igyxb-000LO1-Bl for ged-emacs-devel@m.gmane.org; Mon, 16 Dec 2019 23:35:27 +0100 Original-Received: from localhost ([::1]:32862 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1igyxZ-0007GN-PV for ged-emacs-devel@m.gmane.org; Mon, 16 Dec 2019 17:35:25 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46879) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1igyx7-0006ox-A0 for emacs-devel@gnu.org; Mon, 16 Dec 2019 17:34:58 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1igyx6-00023w-7L for emacs-devel@gnu.org; Mon, 16 Dec 2019 17:34:57 -0500 Original-Received: from mail-wr1-x434.google.com ([2a00:1450:4864:20::434]:39527) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1igyx6-00020i-1w for emacs-devel@gnu.org; Mon, 16 Dec 2019 17:34:56 -0500 Original-Received: by mail-wr1-x434.google.com with SMTP id y11so9191885wrt.6 for ; Mon, 16 Dec 2019 14:34:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=wq+DXd09DZcALQzYCOADRuk1HLgxJMqlyF/A+5s+6cc=; b=H32XlXsNk3kWrkd2svX/37paX7FSed+e9wr11Gyz8JLO6G12HAQmExAITG7Q6tpGMO uUwL9nwuZc+0Gdx9MENMvEsFT72ehy/AjeWJXHpuPZug2nhAnBNzIh7XBtdSKS9mZJEz xBJciT7971PDZbTn9tA3D2u2yICxXuAFZTVM6r34q5+Gv9kr5yVF/v1629Ly6xSDpR3K 8/0M6QKrwR/Tk7Unp9M3irVoMzFpHVBePnKpMu8EvEnQ5UCf7ScsWyjAl21E1PpmDdR3 WPC7pPvqVYbLJ17QVqqfPNOyDc3V1WQjB4gLCveBzdBsedCua5jvIMLyOSGqvNw1DlTP LezQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=wq+DXd09DZcALQzYCOADRuk1HLgxJMqlyF/A+5s+6cc=; b=opDKyJAzdxmzofCoQ2UIkybGGmAQJZuZnEJ2IAQK9KYG+y7heVAfMEjzT/RZF0QcnU C+u+VNA3MRc09y9kR/W/dd+SlxpeeW0RFPiXPwNqoXmt7tq0jld4EQXisCoQhqIF/Tle oJmoEyVoGTHu42ZvmcGNLnSjJncLfJvOO9BmS39XQTMYdDo7P6XvNcjr54ZaSqbFhxPx TNKG2SsMoGHgDJjmdcoLUlo+qGTvU6/mHSK9LDtHk7aXj85c474/e+jD6WNBlxagJRYA lMIcoTZnEynVlcOJGfPuQRUiMXCgOyH9H+RjwQ7TDnW3BXi/YrGtQrzcgzs6tMq8rLCN zOIg== X-Gm-Message-State: APjAAAV3WoOAU0qfIv7wF6Al00vB0dZvQPlHR3uWY+wO3vLlK2LqbchF OIMZvsGysY/a7Ob7bdkUjRxmQD14C8nMeX9L1EraMQ4= X-Google-Smtp-Source: APXvYqzZ+WBRC3i5bMpLskym9XtCmy5pSpNYJ3dgAqN6JPSHAehQQdSAOaj/4HxNX9Dpk+vAQrxmp/oL4/X+V3n1trA= X-Received: by 2002:adf:cd0a:: with SMTP id w10mr32180271wrm.107.1576535693616; Mon, 16 Dec 2019 14:34:53 -0800 (PST) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::434 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:243431 Archived-At: Apparently it is because of this commit: 7228488effa78dcb75284cb6d247b24804e0e7f5 Author: Stefan Monnier 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