unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Protesilaos Stavrou <info@protesilaos.com>
Cc: Alan Mackenzie <acm@muc.de>, 55414@debbugs.gnu.org
Subject: bug#55414: 29.0.50; Byte compilation error for the modus-themes
Date: Sun, 15 May 2022 15:45:19 +0200	[thread overview]
Message-ID: <874k1qj4eo.fsf@gnus.org> (raw)
In-Reply-To: <87lev46l8y.fsf@protesilaos.com> (Protesilaos Stavrou's message of "Sat, 14 May 2022 21:07:41 +0300")

Protesilaos Stavrou <info@protesilaos.com> writes:

> Since commit 850074636e73509b09c28e965c1af054a84f4069, my modus-themes
> no longer byte compile when installing from source.  The message is:
>
>     Error: Lisp nesting exceeds ‘max-lisp-eval-depth’

Could you switch on debug-on-error and post the backtrace?  It'd be
interesting to see whether it's inflooping or whether the eval depth
really is just too small.

We've seen similar things (i.e., Emacs now using a bigger depth to
compile) with other modules after the symbols-with-positions feature was
added, so I've added Alan to the CCs; perhaps he has some comments.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-05-15 13:45 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 [this message]
     [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
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=874k1qj4eo.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=55414@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=info@protesilaos.com \
    /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).