[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: debugging post command hook max-lisp-eval-depth
From: |
Leo Liu |
Subject: |
Re: debugging post command hook max-lisp-eval-depth |
Date: |
Fri, 22 Jun 2018 12:38:56 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.1 (macOS 10.12.6) |
On 2018-06-20 17:53 -0400, Stefan Monnier wrote:
>> have any recursive calls.
>
> I'd look at some code shared by the two minor modes, tho maybe it
> happened via an advice or a function place on both minor mode's hooks
> (i.e. the minor modes aren't directly related, except as "vehicles").
I wonder if this is a similar bug https://debbugs.gnu.org/31793. There
is a recipe to reliably render emacs unusable in the report.
Leo
- debugging post command hook max-lisp-eval-depth, John Shahid, 2018/06/17
- Re: debugging post command hook max-lisp-eval-depth, Stefan Monnier, 2018/06/17
- Re: debugging post command hook max-lisp-eval-depth, John Shahid, 2018/06/17
- Re: debugging post command hook max-lisp-eval-depth, Stefan Monnier, 2018/06/18
- Re: debugging post command hook max-lisp-eval-depth, John Shahid, 2018/06/18
- Re: debugging post command hook max-lisp-eval-depth, Stefan Monnier, 2018/06/18
- Re: debugging post command hook max-lisp-eval-depth, John Shahid, 2018/06/18
- Re: debugging post command hook max-lisp-eval-depth, John Shahid, 2018/06/20
- Re: debugging post command hook max-lisp-eval-depth, Stefan Monnier, 2018/06/20
- Re: debugging post command hook max-lisp-eval-depth,
Leo Liu <=
- Re: debugging post command hook max-lisp-eval-depth, John Shahid, 2018/06/23