From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>
Cc: 57911@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#57911: Abolish max-specpdl-size
Date: Mon, 19 Sep 2022 08:27:35 -0400 [thread overview]
Message-ID: <jwv5yhjwnvx.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <D6C5C246-4DF2-4859-B447-7BA0E4FD0489@gmail.com> ("Mattias Engdegård"'s message of "Mon, 19 Sep 2022 11:35:24 +0200")
Mattias Engdegård [2022-09-19 11:35:24] wrote:
> diff --git a/lisp/subr.el b/lisp/subr.el
> index d7cdc28abb..0e8cb2fcd6 100644
> --- a/lisp/subr.el
> +++ b/lisp/subr.el
> @@ -376,6 +376,13 @@ ignore-error
> \f
> ;;;; Basic Lisp functions.
>
> +(defvar max-specpdl-size 2500
> + "Former limit on specbindings, now without effect.
> +This variable used to limit the size of the specpdl stack which,
> +among other things, held dynamic variable bindings and `unwind-protect'
> +activations. To prevent runaway recursion, use `max-lisp-eval-lisp-depth'
> +instead; it will indirectly limit the specpdl stack size as well.")
> +
> (defvar gensym-counter 0
> "Number used to construct the name of the next symbol created by `gensym'.")
Please mark it as obsolete as well.
Stefan
next prev parent reply other threads:[~2022-09-19 12:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 11:57 bug#57911: Abolish max-specpdl-size Mattias Engdegård
2022-09-19 7:10 ` Lars Ingebrigtsen
2022-09-19 9:35 ` Mattias Engdegård
2022-09-19 12:27 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-09-19 15:35 ` Mattias Engdegård
2022-09-19 16:52 ` Michael Albinus
2022-09-19 17:09 ` Lars Ingebrigtsen
2022-09-19 17:30 ` Michael Albinus
2022-09-19 18:25 ` Lars Ingebrigtsen
2022-09-20 12:23 ` Visuwesh
2022-09-20 15:52 ` Eli Zaretskii
2022-09-20 16:23 ` Visuwesh
2022-09-20 16:30 ` Eli Zaretskii
2022-09-20 16:30 ` Lars Ingebrigtsen
2022-09-20 16:36 ` Eli Zaretskii
2022-09-20 16:48 ` Lars Ingebrigtsen
2022-09-20 17:27 ` Eli Zaretskii
2022-09-21 11:04 ` Lars Ingebrigtsen
2022-09-20 21:51 ` Gregory Heytings
2022-09-20 20:32 ` Lars Ingebrigtsen
2022-09-21 0:02 ` Gregory Heytings
2022-09-19 17:28 ` Mattias Engdegård
2022-09-19 12:40 ` Lars Ingebrigtsen
2022-09-19 13:54 ` Eli Zaretskii
2022-09-19 17:36 ` Mattias Engdegård
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=jwv5yhjwnvx.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=57911@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mattias.engdegard@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).