From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Upgrading elpa packages results in Lisp nesting exceeds max-lisp-eval-depth...
Date: Sun, 06 Oct 2019 13:58:17 -0400 [thread overview]
Message-ID: <jwva7adrc6i.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 87muedsrgo.fsf@web.de
>> Indeed it's a bug in async.el.
>> Does the patch below help?
> I can't really test anymore, since all packages are updated now...but
> evaluating (async-bytecomp-get-allowed-pkgs) gives me
There's no async-bytecomp-get-allowed-pkgs any more, so if you're still
using it, it will break because it uses the old calling convention of
async-bytecomp--get-package-deps (which took a single package whereas
now it takes a list of packages).
> Even harder to test now since the fixed helm package appeared in this moment.
Actually, the most important test is to make sure it still works
correctly: I'm pretty sure it fixes the inf-recursion.
Stefan
next prev parent reply other threads:[~2019-10-06 17:58 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
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 [this message]
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
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=jwva7adrc6i.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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.
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).