From: Oleksandr Gavenko <gavenkoa@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: max-lisp-eval-depth
Date: Thu, 31 Jan 2013 20:28:54 +0200 [thread overview]
Message-ID: <87a9rpcil5.fsf@gavenkoa.example.com> (raw)
In-Reply-To: jwvvcae8h9h.fsf-monnier+gnu.emacs.help@gnu.org
On 2013-01-31, Stefan Monnier wrote:
>> And then other times, I can't enter my Inbox because of
>> "max-lisp-eval-depth."
>
> That's either because there's an infinite recursion (in which case you
> need to fix the corresponding code), or because the code uses more stack
> space than provided.
> You can fix the latter problem either by increasing the stack space (by
> setting max-lisp-eval-depth to a larger value) or by reducing the
> stack usage. Byte-compiled code uses much less stack space, so if you
> use Elisp packages without byte-compiling them, the first thing I'd
> suggest is to byte-compile them.
>
Please answer why *Byte-compiled code uses much less stack space*?
Very briefly, with few tech details. Which ratio between compiled and
non-compiled usage?
--
Best regards!
next prev parent reply other threads:[~2013-01-31 18:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.18654.1359574929.855.help-gnu-emacs@gnu.org>
2013-01-30 22:01 ` max-lisp-eval-depth Stefan Monnier
2013-01-31 3:08 ` max-lisp-eval-depth drain
[not found] ` <mailman.18689.1359601697.855.help-gnu-emacs@gnu.org>
2013-01-31 14:54 ` max-lisp-eval-depth jack-mac
2013-01-31 15:04 ` max-lisp-eval-depth Ludwig, Mark
2013-01-31 17:33 ` max-lisp-eval-depth drain
2013-01-31 18:28 ` Oleksandr Gavenko [this message]
2013-02-01 20:46 ` max-lisp-eval-depth Stefan Monnier
2013-02-02 19:25 ` max-lisp-eval-depth drain
2013-02-02 19:27 ` max-lisp-eval-depth Drew Adams
2013-02-03 4:53 ` max-lisp-eval-depth drain
2013-01-30 19:42 max-lisp-eval-depth drain
2013-01-30 20:00 ` max-lisp-eval-depth Perry Smith
2013-01-30 21:27 ` max-lisp-eval-depth Drew Adams
2013-01-30 22:00 ` max-lisp-eval-depth drain
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=87a9rpcil5.fsf@gavenkoa.example.com \
--to=gavenkoa@gmail.com \
--cc=help-gnu-emacs@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 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.