unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Protesilaos Stavrou <info@protesilaos.com>
Cc: acm@muc.de, larsi@gnus.org, 55414@debbugs.gnu.org
Subject: bug#55414: 29.0.50; Byte compilation error for the modus-themes
Date: Wed, 25 May 2022 16:12:37 +0300	[thread overview]
Message-ID: <83r14h4uyi.fsf@gnu.org> (raw)
In-Reply-To: <87h75el2f5.fsf@protesilaos.com> (message from Protesilaos Stavrou on Wed, 25 May 2022 06:24:46 +0300)

> From: Protesilaos Stavrou <info@protesilaos.com>
> Cc: acm@muc.de, larsi@gnus.org, 55414@debbugs.gnu.org
> Date: Wed, 25 May 2022 06:24:46 +0300
> 
> The first approach was to add the following at the end of the relevant
> files:
> 
>     ;; Local Variables:
>     ;; max-lisp-eval-depth: 3000
>     ;; max-specpdl-size: 3000
>     ;; End:
> 
> Then M-x byte-compile-file with modus-operandi-theme.el: the local
> variables were ignored.  Same for:
> 
>     (package-install-file "/preferred/path/to/modus-themes")
> 
> The second approach I tried was to add those variables in a
> .dir-locals.el file which was located in the same directory as the
> modus-themes.  The contents of that file looked like this:
> 
>     ((emacs-lisp-mode . ((max-lisp-eval-depth . 3000)
>                          (max-specpdl-size . 3000))))
> 
> Again, the values were ignored.

How about advising package-install-file?

Also, how do other packages overcome similar problems?  Surely, this
isn't the first or the second package that needs such measures?

And finally, any ideas why a package that is just a theme need such
large values of these variables?

> These methods work for other variables but not those two.  Perhaps
> because they are considered "risky" as file-local?

No, I think that's because these facilities visit the file literally.

> > If the above misses the point, please tell more how you compile the
> > package and how you tried to enlarge the values of those variables.
> 
> I don't use a Makefile.  The recipe I shared in the first message to
> this bug report affects installation via package.el and, by extension,
> GNU ELPA.

If all else fails, perhaps package.el should acquire a feature whereby
these variables could be overridden during byte-compilation.





  reply	other threads:[~2022-05-25 13:12 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-14 18:07 bug#55414: 29.0.50; Byte compilation error for the modus-themes Protesilaos Stavrou
2022-05-15 13:45 ` Lars Ingebrigtsen
     [not found]   ` <87lev296hl.fsf@protesilaos.com>
2022-05-15 15:16     ` Lars Ingebrigtsen
2022-05-16  7:58       ` Alan Mackenzie
2022-05-16  8:21         ` Protesilaos Stavrou
2022-05-16 11:15         ` Eli Zaretskii
2022-05-16 12:03           ` Alan Mackenzie
2022-05-16 12:26             ` Eli Zaretskii
2022-05-16 13:48               ` Alan Mackenzie
2022-05-16 13:56                 ` Eli Zaretskii
2022-05-16 14:52                   ` Protesilaos Stavrou
2022-05-16 15:56                     ` Eli Zaretskii
2022-05-22 13:10                       ` Alan Mackenzie
2022-05-22 13:25                         ` Eli Zaretskii
2022-05-23  3:51                           ` Protesilaos Stavrou
2022-05-23 10:57                             ` Eli Zaretskii
2022-05-24  4:37                               ` Protesilaos Stavrou
2022-05-24 11:09                                 ` Eli Zaretskii
2022-05-25  3:24                                   ` Protesilaos Stavrou
2022-05-25 13:12                                     ` Eli Zaretskii [this message]
2022-05-26  5:55                                       ` Protesilaos Stavrou
2022-05-26 11:32                                         ` Eli Zaretskii
2022-05-26 11:57                                           ` Lars Ingebrigtsen
2022-05-26 12:59                                             ` Eli Zaretskii
2022-05-26 15:20                                             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-26 15:42                                               ` Protesilaos Stavrou
2022-05-27  9:52                                             ` Alan Mackenzie
2022-05-27 10:25                                               ` Lars Ingebrigtsen
2022-05-26 16:02               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-26 15:30 ` Mattias Engdegård
2022-05-27  9:03   ` Mattias Engdegård
2022-05-27 10:23     ` Lars Ingebrigtsen
2022-05-27 10:39       ` Protesilaos Stavrou
2022-05-27 10:42         ` Lars Ingebrigtsen
2022-05-27 11:32           ` Alan Mackenzie
2022-05-27 11:52             ` Lars Ingebrigtsen
2022-05-27 13:42               ` Alan Mackenzie
2022-05-27 13:50                 ` Lars Ingebrigtsen
2022-05-28 23:13                   ` Richard Stallman
2022-05-27 12:15             ` Protesilaos Stavrou
2022-05-27 13:59   ` Alan Mackenzie
2022-05-27 16:53     ` Mattias Engdegård
2022-05-27 18:24       ` Alan Mackenzie
2022-05-29  9:18         ` Mattias Engdegård
2022-05-29 13:38           ` Alan Mackenzie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83r14h4uyi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=55414@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=info@protesilaos.com \
    --cc=larsi@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).