From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Why is it so difficult to get a Lisp backtrace? Date: Sat, 25 Jun 2022 19:51:59 +0300 Message-ID: <83sfnsadow.fsf@gnu.org> References: <87edzchi3d.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7452"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jun 25 18:54:05 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o592q-0001l7-Dt for ged-emacs-devel@m.gmane-mx.org; Sat, 25 Jun 2022 18:54:04 +0200 Original-Received: from localhost ([::1]:56440 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o592p-0004ha-00 for ged-emacs-devel@m.gmane-mx.org; Sat, 25 Jun 2022 12:54:03 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43502) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o590v-00030P-PU for emacs-devel@gnu.org; Sat, 25 Jun 2022 12:52:06 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:35050) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o590u-0002pt-J4; Sat, 25 Jun 2022 12:52:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=YLygp4hKSa2XkOEBGVgfqkFixYM78IQdu7wTgrU1m4o=; b=ope6USjetnJj TlKi+Zs3RBIagLQ4fMkClLXsDLTlFaCHnZbInHPNFd8JpypgCX0T65U/+tVWRjiMOK6sqSLTOyDwC VkS2RgMwjTcWiXcGSK5a54siuFDxZTcTwxO/GKnmnbN9zQIU82o5ZRiNxVIej+cwoECU6kAhsfJlg G1iSUy/idjIjeP2iKgMzc6fRXDWIZfO14GJeQrfg0S81+mnwYvTVWELBYRSHyMg2AE697MqwogsqR FuO2xS3Kb0dbtcq6xstR6mw5NuEZnO3RKuCeLltgFBhnnE2MEr+kafoQjLJj+B9Ruu3svbGPe7r0N NRwk7iJnq8lBLUbTMdflxw==; Original-Received: from [87.69.77.57] (port=1435 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o590s-0005Z9-Ez; Sat, 25 Jun 2022 12:52:04 -0400 In-Reply-To: (message from Alan Mackenzie on Sat, 25 Jun 2022 15:59:52 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:291622 Archived-At: > Date: Sat, 25 Jun 2022 15:59:52 +0000 > Cc: emacs-devel@gnu.org > From: Alan Mackenzie > > Another thing I'd like to be able to do is get a backtrace when there's > an error in font-locking during redisplay. That's a whole order of > magnitude difference in complexity. The only two ways of having that, AFAIK, are: . emit the backtrace int *Messages* . add the backtrace to delayed-warnings-list You _cannot_ have a *backtrace* buffer popping up when the error comes from some Lisp called by redisplay, because we explicitly disable that, and for a good reason.