GNU bug report logs - #55414
29.0.50; Byte compilation error for the modus-themes

Previous Next

Full log

Message #29 received at 55414 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Alan Mackenzie <acm <at> muc.de>
Cc: larsi <at> gnus.org, info <at> protesilaos.com, 55414 <at> debbugs.gnu.org
Subject: Re: bug#55414: 29.0.50; Byte compilation error for the modus-themes
Date: Mon, 16 May 2022 15:26:57 +0300

> Date: Mon, 16 May 2022 12:03:05 +0000
> Cc: larsi <at> gnus.org, info <at> protesilaos.com, 55414 <at> debbugs.gnu.org
> From: Alan Mackenzie <acm <at> muc.de>
> 
> > > 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?

> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.