[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: debugging post command hook max-lisp-eval-depth
From: |
John Shahid |
Subject: |
Re: debugging post command hook max-lisp-eval-depth |
Date: |
Sat, 23 Jun 2018 15:15:35 +0000 |
User-agent: |
mu4e 1.1.0; emacs 27.0.50 |
Leo Liu <sdl.web@gmail.com> writes:
> 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.
I submitted a patch for the bug you mentioned above. I'm not sure if I'm
running into the same problem as you are. Either way, I'll run with the
patch for a few days to see whether it fixes my issue.
- 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, 2018/06/22
- Re: debugging post command hook max-lisp-eval-depth,
John Shahid <=