unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: max-specpdl-size (was: master df49e3a3ab 3/3: Merge branch 'master' of /home/acm/emacs/emacs.git/master)
Date: Sun, 30 Jan 2022 11:15:33 -0500	[thread overview]
Message-ID: <jwvilu1rykz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <YfZeAFvEx1i/Yx0A@ACM> (Alan Mackenzie's message of "Sun, 30 Jan 2022 09:44:32 +0000")

> As I said earlier, I only saw one of these on a vanilla ./configure.  The
> problem was in max_specpdl_size (2500) being inadequate for the
> generation of leim-list.el.

Reminds me: why do we have/need max-specpdl-size?
AFAICT it's redundant with `max-lisp-eval-depth`.


        Stefan




      parent reply	other threads:[~2022-01-30 16:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <164287475407.1069.3099043415463495481@vcs2.savannah.gnu.org>
     [not found] ` <20220122180558.93F3CC0DA32@vcs2.savannah.gnu.org>
2022-01-24  8:12   ` master df49e3a3ab 3/3: Merge branch 'master' of /home/acm/emacs/emacs.git/master Lars Ingebrigtsen
2022-01-24 11:25     ` Alan Mackenzie
2022-01-24 11:29       ` Lars Ingebrigtsen
2022-01-24 11:44         ` Alan Mackenzie
2022-01-29 11:41           ` Alan Mackenzie
2022-01-24 13:45         ` Lars Ingebrigtsen
2022-01-29 12:12           ` Alan Mackenzie
2022-01-30  9:44     ` Alan Mackenzie
2022-01-30 16:09       ` Lars Ingebrigtsen
2022-01-30 16:39         ` Alan Mackenzie
2022-01-30 17:08           ` Lars Ingebrigtsen
2022-01-30 18:26             ` Lars Ingebrigtsen
2022-01-31 18:37               ` Alan Mackenzie
2022-01-31 18:51                 ` Lars Ingebrigtsen
2022-01-31 19:25                   ` Stefan Monnier
2022-01-31 19:51                   ` Alan Mackenzie
2022-01-31 21:35                   ` Stefan Monnier
2022-01-31 21:36                     ` Lars Ingebrigtsen
2022-01-30 16:15       ` Stefan Monnier [this message]

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=jwvilu1rykz.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.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).