[Top][All Lists]

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

Re: Blink cursor changes, possible W32 breakage.

From: Jan Djärv
Subject: Re: Blink cursor changes, possible W32 breakage.
Date: Wed, 17 Jul 2013 20:53:04 +0200


17 jul 2013 kl. 19:05 skrev Eli Zaretskii <address@hidden>:

>> From: Jan Djärv <address@hidden>
>> Date: Wed, 17 Jul 2013 18:29:46 +0200
>> Cc: address@hidden,
>> address@hidden
>>>> We can't know what other timers do, in general.  Maybe they are supposed 
>>>> to run some Elisp in the background and/or when the frame has no focus.  
>>>> In contrast, we know very well what blinking timers are supposed to do, so 
>>>> we have control over those.
>>> But if you stop one timer, but leave the other N running, what did you
>>> accomplish, exactly, in terms of allowing the laptop stop using
>>> battery power and perhaps swap Emacs out of RAM?
>> In the default configuration, i.e. starting Emacs, editing files and so on, 
>> the only repeating timer there is is the blinking timer, there are no N 
>> other timers.  So for the majority of setups, this is a win.
> I don't think it's a majority, not even close.  The only situation
> that will certainly win here is "emacs -Q", but I wonder whether we
> should optimize that one.

What would those timers be for then?  I can't find a single periodic timer 
except blink timer that is on by default.  Also, why are you against reducing 
Emacs CPU-usage?  It is always a good thing IMHO, excpet when it becomes too 

        Jan D.

reply via email to

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