all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Shahid <jvshahid@gmail.com>
To: Leo Liu <sdl.web@gmail.com>
Cc: 31793@debbugs.gnu.org
Subject: bug#31793: 26.1; (error "Lisp nesting exceeds ‘max-lisp-eval-depth’")
Date: Mon, 25 Jun 2018 13:59:13 +0000	[thread overview]
Message-ID: <87tvprq85q.fsf@gmail.com> (raw)
In-Reply-To: <m1r2kwd1xr.fsf@gmail.com>


Leo Liu <sdl.web@gmail.com> writes:

> On 2018-06-23 15:47 +0000, John Shahid wrote:
>> That seems to be a result of converting `global-eldoc-mode' to use
>> `define-globalized-minor-mode' in 2349f.
>
> Do you happen to know why post-command-hook doesn't protect itself from
> this error?

This is due to the globalized minor mode re-adding itself to the
`post-command-hook' in `,MODE-cmhh'. This only happens when the
major-mode changes in some buffer. In other words, you will run into
this only when trying to switch buffers or use the minibuffer. You can
still navigate the file, i.e. `next-line' is usually fine for me.

> This bug looks very serious because having to kill -9 emacs is
> serious.

I agree, but I can't think of a better way to avoid this problem aside
from the patch I attached earlier.

cheers,

-js





  reply	other threads:[~2018-06-25 13:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12  2:32 bug#31793: 26.1; (error "Lisp nesting exceeds ‘max-lisp-eval-depth’") Leo Liu
2018-06-12  4:43 ` Leo Liu
2018-06-12  4:59   ` Leo Liu
2018-06-12  5:21     ` Eli Zaretskii
2018-06-12  8:46       ` Leo Liu
2018-06-23 15:47         ` John Shahid
2018-06-24  8:27           ` Leo Liu
2018-06-25 13:59             ` John Shahid [this message]
2018-06-25 16:24             ` Noam Postavsky
2018-07-03 16:43           ` John Shahid
2018-07-04 22:38             ` Noam Postavsky
2018-07-05 13:59               ` Eli Zaretskii
2018-07-05 16:33                 ` John Shahid
2018-07-10 12:17                   ` Noam Postavsky
2018-06-12  5:04   ` Eli Zaretskii
2018-06-12  5:24     ` Leo Liu

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=87tvprq85q.fsf@gmail.com \
    --to=jvshahid@gmail.com \
    --cc=31793@debbugs.gnu.org \
    --cc=sdl.web@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.