From: Michael Heerdegen <michael_heerdegen@web.de>
To: Carlo Tambuatco <oraclmaster@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Upgrading elpa packages results in Lisp nesting exceeds max-lisp-eval-depth...
Date: Sun, 06 Oct 2019 16:59:39 +0200 [thread overview]
Message-ID: <87y2xxhqck.fsf@web.de> (raw)
In-Reply-To: <5BA693B5-2A12-46F7-BE5F-8EE8D5215452@gmail.com> (Carlo Tambuatco's message of "Sun, 6 Oct 2019 10:43:10 -0400")
Carlo Tambuatco <oraclmaster@gmail.com> writes:
> During routine upgrading of my installed elpa packages via:
>
> M-x package-list-packages
> U
> x
>
> the package manager just kind of downloads the requested packages,
> then when the compilation starts, it dies after about one second with
> the message: Lisp nesting exceeds max-lisp-eval-depth
>
> I get the error message listed above and the package manager simply
> fails to compile the files...
>
> This only started happening today, it has never happened before. This
> happens regardless of which packages
> I am upgrading.
>
> Any help appreciated...
I have heard that an recursive dependency of Helm packages is the
culprit (helm vs. helm-org or so). Not your fault. I think it will be
fixed soon.
Michael.
next prev parent reply other threads:[~2019-10-06 14:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 14:43 Upgrading elpa packages results in Lisp nesting exceeds max-lisp-eval-depth Carlo Tambuatco
2019-10-06 14:54 ` Joost Kremers
2019-10-06 14:59 ` Michael Heerdegen [this message]
2019-10-06 15:05 ` Joost Kremers
2019-10-06 15:24 ` Michael Heerdegen
2019-10-06 17:11 ` Stefan Monnier
2019-10-06 17:40 ` Michael Heerdegen
2019-10-06 17:46 ` Michael Heerdegen
2019-10-06 17:58 ` Stefan Monnier
2019-10-06 17:55 ` Stefan Monnier
2019-10-06 18:55 ` Michael Heerdegen
2019-10-07 15:57 ` Michael Heerdegen
2019-10-07 17:00 ` Michael Heerdegen
2019-10-07 21:09 ` Stefan Monnier
2019-10-08 13:48 ` Stefan Monnier
2019-10-06 16:52 ` Carlo Tambuatco
2019-10-06 16:58 ` Michael Heerdegen
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=87y2xxhqck.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=oraclmaster@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.