[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: |
Fri, 01 Jul 2022 08:39:31 +0300 |
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Eli Zaretskii <eliz@gnu.org>, larsi@gnus.org, emacs-devel@gnu.org
> Date: Thu, 30 Jun 2022 16:34:23 -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.
- Re: Fontification error backtrace [Was: Why is it so difficult to get a Lisp backtrace?],
Eli Zaretskii <=