emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Three strikes them out


From: Lennart Borgman (gmail)
Subject: Re: Three strikes them out
Date: Sat, 31 May 2008 13:58:58 +0200
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666

martin rudalics wrote:
 > What happens when you set `jit-lock-context-time' to a very large value?
 >
 > I can dig up one of those cases that loops and try it, but why do you
 > propose that? (It might of course help a bit to find out where the
 > problem happens and I have one case where this could indeed be
 > interesting, but I am not sure if that is what you mean.)

If font-lock loops within contextual refontification there's either a
bug in font-lock (which I consider highly impropable) or there's a bug
in your code (maybe some function called by a hook or another timer)
that changes the buffer and re-triggers contextual refontification.
Whatever applies should be resolved.

Thanks. The situation is a bit different in my case, but it could perhaps be that contextual refontificaion is re-triggered. Could that happen when the code runs under font-lock and only text properties and overlays are changed?

 > The general problem that looping in a timer may hang Emacs is what I
 > really wanted to address here.

You can't: As soon as you manage to exit looping, a repeating idle timer
will fire again.

Yes, that was why I suggested that we implement something that allows us to stop this (with for example C-g C-g C-g).




reply via email to

[Prev in Thread] Current Thread [Next in Thread]