From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Making Emacs Lisp easier to debug
Date: Sat, 11 Nov 2023 11:04:01 +0000 [thread overview]
Message-ID: <ZU9foXEc56cI5Hyg@ACM> (raw)
In-Reply-To: <838r74ye77.fsf@gnu.org>
Hello, Eli.
On Sat, Nov 11, 2023 at 08:52:12 +0200, Eli Zaretskii wrote:
> > Date: Fri, 10 Nov 2023 20:56:54 +0000
> > From: Alan Mackenzie <acm@muc.de>
> > (ii) Edebugging font locking code. It would be nice to be able to debug
> > font locking code which is being called from redisplay, as well as other
> > hooks which are also called from redisplay. At the moment this isn't
> > possible. To make it possible would require redisplay to become
> > reentrant, so that a frame or window in the inner redisplay call
> > could be where debugging of the outer redisplay call happens. I don't
> > know how practicable it would be to enhance redisplay for this (it is
> > certainly possible). Has anybody ever looked into this before?
> Yes, see jit-lock-debug-mode. (It's described in the ELisp manual.)
:-) I really meant has anybody looked into making redisplay reentrant.
As for jit-lock-debug-mode, it doesn't work in my setup. It just
disables font-lock totally. I suspect its timer isn't triggering for
some reason. I haven't actually tried it yet in emacs -Q.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2023-11-11 11:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 20:56 Making Emacs Lisp easier to debug Alan Mackenzie
2023-11-11 6:52 ` Eli Zaretskii
2023-11-11 9:01 ` Ihor Radchenko
2023-11-11 11:04 ` Alan Mackenzie [this message]
2023-11-11 11:10 ` Eli Zaretskii
2023-11-11 12:10 ` Alan Mackenzie
2023-11-11 13:47 ` Eli Zaretskii
2023-11-11 14:56 ` Alan Mackenzie
2023-11-11 16:01 ` Eli Zaretskii
2023-11-11 17:23 ` Alan Mackenzie
2023-11-11 17:54 ` Eli Zaretskii
2023-11-11 19:55 ` Alan Mackenzie
2023-11-12 7:17 ` Eli Zaretskii
2023-11-12 12:08 ` Alan Mackenzie
2023-11-12 12:28 ` Eli Zaretskii
2023-11-13 18:20 ` XY Problems (tangent, related to common discussion issue here) chad
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZU9foXEc56cI5Hyg@ACM \
--to=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).