all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 18:58:43 +0200	[thread overview]
Message-ID: <87sgo5stdo.fsf@web.de> (raw)
In-Reply-To: <49D14778-DA0A-4EB7-8C37-92F507892BD5@gmail.com> (Carlo Tambuatco's message of "Sun, 6 Oct 2019 12:52:01 -0400")

Carlo Tambuatco <oraclmaster@gmail.com> writes:

> I do have helm installed as well as several other helm dependents..
>
> helm-20191003.727
> helm-core-20191003.1622
> helm-projectile-20190731.1538
>
> Are these causing the problem?

As I said - seems it's already enough to have a repository included that
has these packages (Melpa).  Whether these packages are actually
installed or to be upgraded doesn't seem to matter.

But the helm list reads like they have fixed it so it should start
working again soon.  Just be patient.

Michael.



      reply	other threads:[~2019-10-06 16: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
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 [this message]

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=87sgo5stdo.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.