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 22:14:57 +0300 Organization: LINKOV.NET Message-ID: <86v8sgveqi.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> <868rpd0w1a.fsf@mail.linkov.net> <8335fkes4d.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="28685"; 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: monnier@iro.umontreal.ca, 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:21:02 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 1o7MCM-0007Lh-A7 for ged-emacs-devel@m.gmane-mx.org; Fri, 01 Jul 2022 21:21:02 +0200 Original-Received: from localhost ([::1]:54152 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o7MCJ-0002BZ-UI for ged-emacs-devel@m.gmane-mx.org; Fri, 01 Jul 2022 15:20:59 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55464) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o7MBd-0001Ik-1t for emacs-devel@gnu.org; Fri, 01 Jul 2022 15:20:17 -0400 Original-Received: from relay2-d.mail.gandi.net ([2001:4b98:dc4:8::222]:32969) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o7MBa-0004WE-7N; Fri, 01 Jul 2022 15:20:16 -0400 Original-Received: (Authenticated sender: juri@linkov.net) by mail.gandi.net (Postfix) with ESMTPSA id D411D40007; Fri, 1 Jul 2022 19:20:05 +0000 (UTC) In-Reply-To: <8335fkes4d.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 01 Jul 2022 19:04:50 +0300") Received-SPF: pass client-ip=2001:4b98:dc4:8::222; envelope-from=juri@linkov.net; helo=relay2-d.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:291788 Archived-At: >> 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. > > I don't necessarily object, but I'm asking myself who'd want less than > the complete information. And I don't find any good answer; it seems > to me that whenever one gets the less detailed report, one will > immediately want the most detailed one. More information is better than less, indeed. Then in case someone worries about flooding the Messages buffer, maybe at least hide the complete information, then provide a button to unhide it.