From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.bugs Subject: bug#55414: 29.0.50; Byte compilation error for the modus-themes Date: Mon, 16 May 2022 13:48:27 +0000 Message-ID: References: <87lev46l8y.fsf@protesilaos.com> <874k1qj4eo.fsf@gnus.org> <87lev296hl.fsf@protesilaos.com> <87zgjihlmw.fsf@gnus.org> <83zgjhiv8l.fsf@gnu.org> <83wnelirxq.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11135"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, info@protesilaos.com, 55414@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon May 16 15:49:41 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1nqb6Q-0002ZW-Rs for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 16 May 2022 15:49:38 +0200 Original-Received: from localhost ([::1]:34572 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nqb6P-0000B3-N5 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 16 May 2022 09:49:37 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36352) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nqb5q-0000An-IY for bug-gnu-emacs@gnu.org; Mon, 16 May 2022 09:49:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:58289) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nqb5q-0006m6-A3 for bug-gnu-emacs@gnu.org; Mon, 16 May 2022 09:49:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nqb5q-0008QA-60 for bug-gnu-emacs@gnu.org; Mon, 16 May 2022 09:49:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Alan Mackenzie Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 16 May 2022 13:49:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 55414 X-GNU-PR-Package: emacs Original-Received: via spool by 55414-submit@debbugs.gnu.org id=B55414.165270892032339 (code B ref 55414); Mon, 16 May 2022 13:49:02 +0000 Original-Received: (at 55414) by debbugs.gnu.org; 16 May 2022 13:48:40 +0000 Original-Received: from localhost ([127.0.0.1]:52186 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nqb5Q-0008PU-J0 for submit@debbugs.gnu.org; Mon, 16 May 2022 09:48:39 -0400 Original-Received: from colin.muc.de ([193.149.48.1]:55133 helo=mail.muc.de) by debbugs.gnu.org with smtp (Exim 4.84_2) (envelope-from ) id 1nqb5O-0008PI-Ut for 55414@debbugs.gnu.org; Mon, 16 May 2022 09:48:35 -0400 Original-Received: (qmail 69462 invoked by uid 3782); 16 May 2022 13:48:28 -0000 Original-Received: from acm.muc.de (p4fe15b7d.dip0.t-ipconnect.de [79.225.91.125]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Mon, 16 May 2022 15:48:28 +0200 Original-Received: (qmail 5544 invoked by uid 1000); 16 May 2022 13:48:27 -0000 Content-Disposition: inline In-Reply-To: <83wnelirxq.fsf@gnu.org> X-Submission-Agent: TMDA/1.3.x (Ph3nix) X-Primary-Address: acm@muc.de X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:232388 Archived-At: Hello, Eli. On Mon, May 16, 2022 at 15:26:57 +0300, Eli Zaretskii wrote: > > Date: Mon, 16 May 2022 12:03:05 +0000 > > Cc: larsi@gnus.org, info@protesilaos.com, 55414@debbugs.gnu.org > > From: Alan Mackenzie > > > > If this compilation succeeds, then perhaps we need to increase our > > > > default max-lisp-eval-depth. > > > But do we need to do that by default in Emacs, when the problem is > > > local to this theme? Can't the package arrange for enlarging the > > > threshold only for itself? > > We could. But I get the feeling that there are quite a lot of places > > which increase max-lisp-eval-depth for their own use. > Examples of those places? OK, i've kind of conflated max-lisp-eval-depth with max-specpdl-size, as they seem to be the same sort of thing. In recent months I've increased max-specpdl-size to 5000 in emacs-lisp/comp.el, and also to 5000 (default is 2500) in leim/Makefile.in for the generation of leim-list.el. Also max-specpdl-size to 5000 in admin/grammars/Makefile.in. With a bit of grepping, max-lisp-eval-depth is increased in edebug.el, regexp-opt.el, gnus-sum.el, .... So, apologies, I was thinking more about max-specpdl-size. But surely the default values of both these variables should be sufficiently large to handle almost any evaluation, with only the rarest/most specialised of evaluations needing them increased. > > Put another way, is there any overwhelming disadvantage to having a > > larger default value of max-lisp-eval-depth, and possibly > > max-specpdl-size? > The disadvantage is that higher values prolong the time needed to > detect real infinite recursions, and enlarge the probability of > hitting C stack overflows, whose consequences are much more serious > and harder to endure without losing the session and its edits. Yes. I seem to remember the Elisp manual saying only that these values can be increased considerably without danger. Or something like that. Perhaps we should be a little less vague on this point. -- Alan Mackenzie (Nuremberg, Germany).