Re: Blink cursor changes, possible W32 breakage.

[Stefan Monnier]

>> No, indeed, but they're not activated unless the user asks for
>> it explicitly.
> I don't see how this is relevant.

It's relevant because most optional features are turned off.

> Are we going to tell users not to enable features if they want Emacs
> to be friendly to the batteries?  That's not going to happen.

jit-lock-stealth is pretty clearly battery unfriendly.  It's in its nature.

>> 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.
> JIT Stealth has a variable to limit the system load it imposes; mine
> is set to 20%.

Yes, we did try to make jit-lock-stealth work acceptably, but after many
attempts, we chose to turn it off instead because there's always some
situation where it consumes a lot more CPU than what you'd want.


        Stefan