[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Blink cursor changes, possible W32 breakage.
From: |
Eli Zaretskii |
Subject: |
Re: Blink cursor changes, possible W32 breakage. |
Date: |
Fri, 19 Jul 2013 09:39:37 +0300 |
> From: Miles Bader <address@hidden>
> Cc: Jan Djärv <address@hidden>, address@hidden
> Date: Fri, 19 Jul 2013 11:12:18 +0900
>
> Eli Zaretskii <address@hidden> writes:
> >> What would those timers be for then? I can't find a single periodic
> >> timer except blink timer that is on by default.
> >
> > Like I said, I firmly believe that most Emacs users have many defaults
> > overridden by customizations. Two popular timers that come to my mind
> > are display-time and jit-stealth.
>
> display-time fires once a minute, which is much better than twice a
> second...
Mine fires every 5 seconds (because I want to see the CPU load numbers
up-to-date).
> If jit-lock timers are firing too often, that could certainly be fixed
> too, as there's nothing inherent about that which requires frequently
> firing timers when idle (or even when active, if all jit-locking has
> been completed and jit-lock'd buffers haven't changed)...
>
> It seems sense to fix such things, even if the _immediate_ benefit
> is limited because of remaining issues. One needn't do them all at
> once, and each fixed issue makes things easier in the future.
I'm all for doing all that, and more, to minimize CPU usage when Emacs
is idle. My point was that _without_ a thorough fixing of at least
the most popular timer-based features, just turning off blinking will
not solve the issue at hand for all but the very basic setups.
- Re: Blink cursor changes, possible W32 breakage., (continued)
- Re: Blink cursor changes, possible W32 breakage., Eli Zaretskii, 2013/07/17
- Re: Blink cursor changes, possible W32 breakage., Miles Bader, 2013/07/17
- Re: Blink cursor changes, possible W32 breakage., Jan Djärv, 2013/07/17
- Re: Blink cursor changes, possible W32 breakage., Eli Zaretskii, 2013/07/17
- Re: Blink cursor changes, possible W32 breakage., Jan Djärv, 2013/07/17
- Re: Blink cursor changes, possible W32 breakage., Eli Zaretskii, 2013/07/17
- Re: Blink cursor changes, possible W32 breakage., Jan Djärv, 2013/07/17
- Re: Blink cursor changes, possible W32 breakage., Eli Zaretskii, 2013/07/17
- Re: Blink cursor changes, possible W32 breakage., Jan Djärv, 2013/07/17
- Re: Blink cursor changes, possible W32 breakage., Miles Bader, 2013/07/18
- Re: Blink cursor changes, possible W32 breakage.,
Eli Zaretskii <=
- Re: Blink cursor changes, possible W32 breakage., Stefan Monnier, 2013/07/19
- Re: Blink cursor changes, possible W32 breakage., Eli Zaretskii, 2013/07/19
- Re: Blink cursor changes, possible W32 breakage., Óscar Fuentes, 2013/07/19
- Re: Blink cursor changes, possible W32 breakage., Eli Zaretskii, 2013/07/19
- Re: Blink cursor changes, possible W32 breakage., Óscar Fuentes, 2013/07/19
- Re: Blink cursor changes, possible W32 breakage., Eli Zaretskii, 2013/07/19
- Re: Blink cursor changes, possible W32 breakage., Thien-Thi Nguyen, 2013/07/19
- Re: Blink cursor changes, possible W32 breakage., Stefan Monnier, 2013/07/20
- Re: Blink cursor changes, possible W32 breakage., Eli Zaretskii, 2013/07/20
- Re: Blink cursor changes, possible W32 breakage., Stefan Monnier, 2013/07/20