From: Doug Lewan <dougl@shubertticketing.com>
To: Fabrice Popineau <fabrice.popineau@gmail.com>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Emacs Lisp Depth
Date: Tue, 16 Sep 2014 13:37:45 +0000 [thread overview]
Message-ID: <155DEC68569B714B86C2C7075F5EDA9892B1F71E@DAKIYA1.pegasus.local> (raw)
In-Reply-To: <CAFgFV9PeSNRYJccX1wK-Sd3vfQ94PnKhkKrUz97mMbg=_QuZrA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
No, you're not the only one. I've run across it several times. I'd say about half of them revealed bugs on my part, but there's no doubt that it occasionally has to be raised for legitimate reasons. I assume that the default value is somewhat arbitrary, but chosen pragmatically.
,Doug
Douglas Lewan
Shubert Ticketing
(201) 489-8600 ext 224 or ext 4335
"This is a slow pup," he said continuing his ascent.
From: emacs-orgmode-bounces+dougl=shubertticketing.com@gnu.org [mailto:emacs-orgmode-bounces+dougl=shubertticketing.com@gnu.org] On Behalf Of Fabrice Popineau
Sent: Tuesday, 2014 September 16 09:01
To: emacs-orgmode@gnu.org; Emacs developers
Subject: [O] Emacs Lisp Depth
Hi,
Am I the only one to have hit the bottom of the default max_specpdl_size and max_lisp_eval_depth values ?
I had already set max_specpdl_size to 2600 and I had to raise it again.
I have an Org file of about 10000 lines, and I am exporting x100 beamer slides and a latex document for about 200 pages .
Curious to hear about other reports.
Fabrice
[-- Attachment #2: Type: text/html, Size: 26119 bytes --]
next prev parent reply other threads:[~2014-09-16 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 13:01 Emacs Lisp Depth Fabrice Popineau
2014-09-16 13:37 ` Doug Lewan [this message]
2014-09-16 13:38 ` Nicolas Goaziou
2014-09-21 14:04 ` Grant Rettke
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=155DEC68569B714B86C2C7075F5EDA9892B1F71E@DAKIYA1.pegasus.local \
--to=dougl@shubertticketing.com \
--cc=emacs-devel@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=fabrice.popineau@gmail.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 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.