[Top][All Lists]

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

Re: Blink cursor changes, possible W32 breakage.

From: Stefan Monnier
Subject: Re: Blink cursor changes, possible W32 breakage.
Date: Sun, 21 Jul 2013 22:55:25 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

>> ... they're not activated unless the user asks for
>> it explicitly.
> `jit-lock-context-timer' is activated here though I never asked for it
> "explicitly".

Indeed context refontification is enabled by default, but that's only an
idle timer, so it shouldn't keep firing repeatedly while Emacs is idle.

>> Also jit-lock-stealth used to be enabled by default but
>> was disabled because too many people found it problematic, so only those
>> people who don't care about high/excessive background CPU usage will
>> have it enabled.
> I'm too silly to understand: Don't we talk about the case where Emacs
> remains idle?  Shouldn't these timers trigger once only after that
> happened?

No, the jit-lock-stealth code keeps on running for a potentially long
time after Emacs became idle (IIRC it uses a while-input-pending-p kind
of loop).  But yes, the timer only triggers once.


reply via email to

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