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

Previous Next

Full log

View this message in rfc822 format

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

Good day everyone!

> From: Alan Mackenzie <acm <at> muc.de>
> Date: Sun, 22 May 2022 13:10:20 +0000
>
> There are actually two (or maybe several) pairs of default values for
> max-lisp-eval-depth and max-specpdl-size.  They are set in src/eval.c in
> init_eval_once.  For when native compilation is enabled the defaults are
> 1600/2500.  When it's not, they're 800/1800.
>
> modus-themes needs just short of 3000/3000, presumably when native
> compilation is enabled.

I tried Emacs builds with and without native compilation.  In both
cases, the test succeeds when I set both values close to 3000.

> From: Eli Zaretskii <eliz <at> gnu.org>
> Date: Sun, 22 May 2022 16:25:23 +0300
>
>> Date: Sun, 22 May 2022 13:10:20 +0000
>> Cc: Protesilaos Stavrou <info <at> protesilaos.com>, larsi <at> gnus.org,
>>   55414 <at> debbugs.gnu.org
>> From: Alan Mackenzie <acm <at> muc.de>
>> 
>> It is, in any case, our medium term goal to have native
>> compilation enabled by default.
>
> How does the default value affect this?  I don't want to make the
> values too large for the reasons I've explained up-thread (and you
> agreed, AFAIU).
>
> Do we know what value is necessary for modus-themes to successfully
> byte-compile?  If so, let's increase the value separately for each
> case: byte compilation and native-compilation.

Then I should add local variables?  I am fine with this.  Just need to
have your verdict on the matter.

-- 
Protesilaos Stavrou
https://protesilaos.com

Previous Next

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