[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
Re: Fontification error backtrace [Was: Why is it so difficult to get a Lisp backtrace?]
Fri, 01 Jul 2022 18:34:01 +0300
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (x86_64-pc-linux-gnu)
>> 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.
Also would be nice to introduce a "log level" with possible values
Fatal, Error, Warn, Info, Debug, Trace. Then depending on the
customized value decide whether print the complete backtrace to
the *Messages* buffer, or only the error message, or nothing at all.