[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Fontification error backtrace [Was: Why is it so difficult to get a
|
From: |
Eli Zaretskii |
|
Subject: |
Re: Fontification error backtrace [Was: Why is it so difficult to get a Lisp backtrace?] |
|
Date: |
Sat, 02 Jul 2022 08:53:00 +0300 |
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: acm@muc.de, larsi@gnus.org, emacs-devel@gnu.org
> Date: Fri, 01 Jul 2022 15:26:26 -0400
>
> >> BTW, in order to debug fontification errors, we also have
> >> `jit-locak-debug-mode` which postpones the jit/font-lock execution from
> >> within redisplay to "just a bit later" such that it can use the
> >> debugger. IIRC it still has some rough edges in some cases, but in
> >> theory it should be possible to make this work such that you can (for
> >> example) Edebug `font-lock.el` itself.
> >
> > It would be nice to have this documented in the ELisp manual. I can
> > easily add the jit-lock-debug-mode variable there, but from what you
> > write, there seems to be more wisdom to go with its usage.
>
> No, there's no extra wisdom.
Then what did you mean by "some rough edges in some cases"?