From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov 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 18:34:01 +0300 Organization: LINKOV.NET Message-ID: <868rpd0w1a.fsf@mail.linkov.net> 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="14328"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (x86_64-pc-linux-gnu) Cc: Stefan Monnier , 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 17:51:54 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 1o7Ivy-0003Zr-DO for ged-emacs-devel@m.gmane-mx.org; Fri, 01 Jul 2022 17:51:54 +0200 Original-Received: from localhost ([::1]:41536 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o7Ivx-0006eZ-CK for ged-emacs-devel@m.gmane-mx.org; Fri, 01 Jul 2022 11:51:53 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38370) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o7Iv1-0005ZU-Rv for emacs-devel@gnu.org; Fri, 01 Jul 2022 11:50:55 -0400 Original-Received: from relay10.mail.gandi.net ([217.70.178.230]:39581) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o7Iuy-0006FN-HD; Fri, 01 Jul 2022 11:50:55 -0400 Original-Received: (Authenticated sender: juri@linkov.net) by mail.gandi.net (Postfix) with ESMTPSA id 98016240009; Fri, 1 Jul 2022 15:50:46 +0000 (UTC) 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=217.70.178.230; envelope-from=juri@linkov.net; helo=relay10.mail.gandi.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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:291784 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. Also would be nice to introduce a "log level" with possible values Fatal, Error, Warn, Info, Debug, Trace. Then depending on the customized value decide whether print the complete backtrace to the *Messages* buffer, or only the error message, or nothing at all.