From: Miles Bader <miles@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Jan Djärv" <jan.h.d@swipnet.se>, emacs-devel@gnu.org
Subject: Re: Blink cursor changes, possible W32 breakage.
Date: Fri, 19 Jul 2013 11:12:18 +0900 [thread overview]
Message-ID: <87ip072t8d.fsf@catnip.gol.com> (raw)
In-Reply-To: <83li550z3l.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 17 Jul 2013 22:23:58 +0300")
Eli Zaretskii <eliz@gnu.org> 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...
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.
-miles
--
The key to happiness
is having dreams. [from a fortune cookie]
next prev parent reply other threads:[~2013-07-19 2:12 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 11:48 Blink cursor changes, possible W32 breakage Jan Djärv
2013-07-16 15:55 ` Glenn Morris
2013-07-16 16:15 ` Jan Djärv
2013-07-16 18:29 ` covici
2013-07-16 18:49 ` Eli Zaretskii
2013-07-16 20:19 ` covici
2013-07-16 17:00 ` Juanma Barranquero
2013-07-16 17:39 ` Eli Zaretskii
2013-07-16 18:02 ` Lars Magne Ingebrigtsen
2013-07-16 18:30 ` Eli Zaretskii
2013-07-16 22:05 ` Stefan Monnier
2013-07-16 21:12 ` Jan Djärv
2013-07-16 21:23 ` Lars Magne Ingebrigtsen
2013-07-16 22:04 ` Óscar Fuentes
2013-07-17 1:58 ` Miles Bader
2013-07-17 7:42 ` Jan Djärv
2013-07-17 14:58 ` Eli Zaretskii
2013-07-17 15:02 ` Lars Magne Ingebrigtsen
2013-07-17 8:38 ` Stefan Monnier
2013-07-17 4:04 ` Eli Zaretskii
2013-07-17 4:56 ` Miles Bader
2013-07-17 7:38 ` Jan Djärv
2013-07-17 14:56 ` Eli Zaretskii
2013-07-17 16:29 ` Jan Djärv
2013-07-17 17:05 ` Eli Zaretskii
2013-07-17 18:53 ` Jan Djärv
2013-07-17 19:23 ` Eli Zaretskii
2013-07-17 19:38 ` Jan Djärv
2013-07-19 2:12 ` Miles Bader [this message]
2013-07-19 6:39 ` Eli Zaretskii
2013-07-19 9:33 ` Stefan Monnier
2013-07-19 10:07 ` Eli Zaretskii
2013-07-19 10:50 ` Óscar Fuentes
2013-07-19 11:13 ` Eli Zaretskii
2013-07-19 12:02 ` Óscar Fuentes
2013-07-19 13:43 ` Eli Zaretskii
2013-07-19 17:52 ` Thien-Thi Nguyen
2013-07-20 8:18 ` Stefan Monnier
2013-07-20 9:25 ` Eli Zaretskii
2013-07-20 22:42 ` Stefan Monnier
2013-07-21 2:45 ` Eli Zaretskii
2013-07-21 7:46 ` Stefan Monnier
2013-07-21 15:43 ` Eli Zaretskii
2013-07-22 2:47 ` Stefan Monnier
2013-07-19 10:54 ` Lars Magne Ingebrigtsen
2013-07-19 9:32 ` Stefan Monnier
2013-07-19 10:08 ` Eli Zaretskii
2013-07-20 8:16 ` Stefan Monnier
2013-07-20 9:26 ` Eli Zaretskii
2013-07-20 22:40 ` Stefan Monnier
2013-07-21 2:44 ` Eli Zaretskii
2013-07-21 7:45 ` Stefan Monnier
2013-07-21 15:42 ` Eli Zaretskii
2013-07-22 2:46 ` Stefan Monnier
2013-07-21 9:20 ` martin rudalics
2013-07-22 2:55 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ip072t8d.fsf@catnip.gol.com \
--to=miles@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).