> 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?
It happens with every change of a text property.
>> 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).
Stop what? All idle timers? That's hardly possible if the
timer fires
before you finished typing that key sequence. If, on the
other hand,
you manage earlier keyboard events get through you will stop
all timers
whenever you mishappen to type C-g repeatedly.
If there's a bug fix the bug. If the bug is caused by a
function run by
a timer make the delay larger or run the function manually
to find the
bug. In general any function run by a timer must be safe -
that is exit
quickly wrt real time and never cause any reentrancy.
|
