From: Richard Copley <rcopley@gmail.com>
To: 17517@debbugs.gnu.org, Juanma Barranquero <lekktu@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#17517: Eager macro-expansion failure: (error "Lisp nesting exceeds `max-lisp-eval-depth'")
Date: Sun, 14 Dec 2014 05:53:31 +0000 [thread overview]
Message-ID: <CAPM58ogy+_c5_aL4wNdam+1Tj=1b9FLqiM_4fVCwL+Mghwb=Wg@mail.gmail.com> (raw)
In-Reply-To: <CAAeL0SSM2Ay6n6RQKLPQjirM1YYGKKkVh0ZRrbTGc3of-VW0Og@mail.gmail.com>
I experimented with different settings of max-lisp-eval-depth. I just
changed the default directly in "init_eval_once" in eval.c and
bootstrapped.
With the current value 600 there are hundreds of these warnings.
With 750 there are a few dozen.
With 800 there are none.
In GNU Emacs 25.0.50.1 (x86_64-w64-mingw32)
of 2014-12-12 on MACHINE
Repository revision: 074965f9355b7cc7f7a5f4385a19433e51c8afd2
Windowing system distributor `Microsoft Corp.', version 6.3.9600
Configured using:
`configure --prefix /c/emacs/emacs-20141212-145542
--disable-dependency-tracking
--enable-locallisppath=%emacs_dir%/../site-lisp --with-wide-int
--build=x86_64-w64-mingw32 'CPPFLAGS=-I G:/usr/include -I
C:/GnuWin32/include -march=native -mtune=native' 'LDFLAGS=-L G:/usr/lib
-L C:/GnuWin32/lib''
Configured features:
XPM JPEG TIFF GIF PNG SOUND NOTIFY ACL GNUTLS LIBXML2 ZLIB
next prev parent reply other threads:[~2014-12-14 5:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 8:15 bug#17517: Eager macro-expansion failure: (error "Lisp nesting exceeds `max-lisp-eval-depth'") Juanma Barranquero
2014-05-19 15:40 ` Glenn Morris
2014-05-19 16:14 ` Juanma Barranquero
2014-05-19 16:22 ` Glenn Morris
2014-05-20 14:09 ` Stefan Monnier
2014-05-20 17:41 ` Juanma Barranquero
2014-12-14 5:53 ` Richard Copley [this message]
2015-04-06 15:59 ` bug#17517: Eager macro-expansion failure: (error "Lisp nesting, " Angelo Graziosi
2015-04-06 16:30 ` Eli Zaretskii
2015-04-06 19:56 ` Angelo Graziosi
2015-04-07 6:15 ` Eli Zaretskii
2015-04-08 12:16 ` Angelo Graziosi
2015-04-08 15:25 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPM58ogy+_c5_aL4wNdam+1Tj=1b9FLqiM_4fVCwL+Mghwb=Wg@mail.gmail.com' \
--to=rcopley@gmail.com \
--cc=17517@debbugs.gnu.org \
--cc=lekktu@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.