From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: ofv@wanadoo.es, emacs-devel@gnu.org
Subject: Re: Blink cursor changes, possible W32 breakage.
Date: Sat, 20 Jul 2013 12:25:32 +0300 [thread overview]
Message-ID: <831u6tzipf.fsf@gnu.org> (raw)
In-Reply-To: <jwvehat7ihi.fsf-monnier+emacs@gnu.org>
> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Date: Sat, 20 Jul 2013 04:18:34 -0400
> Cc: Óscar Fuentes <ofv@wanadoo.es>, emacs-devel@gnu.org
>
> > By contrast, if we want the former, then we need an _infrastructure_
> > that would make it easy to stop all or just some of the timers from
> > firing when Emacs is idle, or doesn't have focus, or the machine runs
> > on batteries, or whatever else condition is deemed appropriate.
>
> AFAICT, most timers are already pretty friendly: all idle-timers are
> friendly, so only the repeated non-idle timers are problematic.
So you are saying that just turning off blink-cursor is good enough?
OK, then let's do that and stop talking about timers and stuff.
next prev parent reply other threads:[~2013-07-20 9:25 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
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 [this message]
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=831u6tzipf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=ofv@wanadoo.es \
/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).