From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Fontification error backtrace [Was: Why is it so difficult to get a Lisp backtrace?] Date: Fri, 01 Jul 2022 15:26:26 -0400 Message-ID: References: <87edzchi3d.fsf@gnus.org> <83sfnsadow.fsf@gnu.org> <83o7yg9f0w.fsf@gnu.org> <83r1396lvr.fsf@gnu.org> <83edz87ivz.fsf@gnu.org> <8335flfl2k.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25984"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: acm@muc.de, larsi@gnus.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jul 01 21:27:41 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 1o7MIn-0006XY-7a for ged-emacs-devel@m.gmane-mx.org; Fri, 01 Jul 2022 21:27:41 +0200 Original-Received: from localhost ([::1]:57926 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o7MIm-0005bM-2P for ged-emacs-devel@m.gmane-mx.org; Fri, 01 Jul 2022 15:27:40 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56678) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o7MHi-0004u7-PW for emacs-devel@gnu.org; Fri, 01 Jul 2022 15:26:34 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:1943) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o7MHg-0006q4-5b; Fri, 01 Jul 2022 15:26:33 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 6A039100142; Fri, 1 Jul 2022 15:26:29 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id DDCCE10012C; Fri, 1 Jul 2022 15:26:27 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1656703587; bh=q7eEd+MPicpSxx+wOYiyJS5JVkZh0ee6uLs0JjqeWrU=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=bn7WojYqUh6Qsy4XTL5TXNeDlkQkDa/dXtNnMVLJ5pZ2F07yEB+rA52vNmdFf2Qo2 EkzxJn39Xf4W15jobtH+cx4qm2QDcC7IOnvbAA/vZOkQ9Wi3Cv0Sd87HYn1Qnpv286 3CpAXL/C4N1l2plJNfwvRZt/SzrPwc9c2zBZl9dfxnOJkzdseTFz1oT6JBbJlLkrme iuXE9HTQpguR3VMxIF24E1y98TBKTwgILF7MZ3qC1QNNOVDO0AbtVKEsvy216Zzqis WJtqfnQ9SAmVySHJc8yI0ulXFvNFtQU/GF/ckkRvKVeVTi3w5tkDPuUaVsrSwP7+15 LxOgvyJ9cuabg== Original-Received: from alfajor (unknown [45.72.196.165]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 4C56A1204C5; Fri, 1 Jul 2022 15:26:27 -0400 (EDT) In-Reply-To: <8335flfl2k.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 01 Jul 2022 08:39:31 +0300") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action 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:291789 Archived-At: >> BTW, in order to debug fontification errors, we also have >> `jit-locak-debug-mode` which postpones the jit/font-lock execution from >> within redisplay to "just a bit later" such that it can use the >> debugger. IIRC it still has some rough edges in some cases, but in >> theory it should be possible to make this work such that you can (for >> example) Edebug `font-lock.el` itself. > > It would be nice to have this documented in the ELisp manual. I can > easily add the jit-lock-debug-mode variable there, but from what you > write, there seems to be more wisdom to go with its usage. No, there's no extra wisdom. It's just that it hasn't been used much, so it probably needs refinement. Bug reports would be quite welcome to figure out what needs to be improved. Stefan