Re: Upgrading elpa packages results in Lisp nesting exceeds max-lisp-eval-depth...

[Michael Heerdegen]

Joost Kremers <joostkremers@fastmail.fm> writes:

> I don't know about the OP, but I myself don't use helm and nothing
> helm-related seems to be installed:
>
> ~ $ v .elpa/helm*
> .elpa/helm*: No such file or directory
>
> So why would I get the error, then?

Hmm, the error happens in `async-bytecomp-get-allowed-pkgs', it loops
over `async-bytecomp-allowed-packages' which includes helm (hardcoded in
async-bytecomp.el !).  When you upgrade packages
`async-bytecomp-get-allowed-pkgs' is called and that produces the issue
no matter which packages you have installed.

I guess setting async-bytecomp-allowed-packages to nil could be a
workaround but I don't want to try this now.

Michael.