From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Blink cursor changes, possible W32 breakage. Date: Fri, 19 Jul 2013 09:39:37 +0300 Message-ID: <831u6v12ae.fsf@gnu.org> References: <83oba22ymd.fsf@gnu.org> <6B4F86F0-164D-4CBE-8CD2-9BC9326451C4@swipnet.se> <8361w93k8e.fsf@gnu.org> <871u6x4we0.fsf@catnip.gol.com> <58D8CF7D-C157-4D48-93B4-2EFFAA4AAF61@swipnet.se> <8338rd2q1h.fsf@gnu.org> <534E99D7-CC13-4C8D-A80B-EC00995F741A@swipnet.se> <83txjt15hw.fsf@gnu.org> <83li550z3l.fsf@gnu.org> <87ip072t8d.fsf@catnip.gol.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Trace: ger.gmane.org 1374215973 30685 80.91.229.3 (19 Jul 2013 06:39:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 19 Jul 2013 06:39:33 +0000 (UTC) Cc: jan.h.d@swipnet.se, emacs-devel@gnu.org To: Miles Bader Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 19 08:39:34 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1V04Ll-0004qa-7V for ged-emacs-devel@m.gmane.org; Fri, 19 Jul 2013 08:39:33 +0200 Original-Received: from localhost ([::1]:34108 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V04Lk-0006wZ-RV for ged-emacs-devel@m.gmane.org; Fri, 19 Jul 2013 02:39:32 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39820) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V04Lh-0006u5-Kk for emacs-devel@gnu.org; Fri, 19 Jul 2013 02:39:30 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V04Lg-0001hz-Mr for emacs-devel@gnu.org; Fri, 19 Jul 2013 02:39:29 -0400 Original-Received: from mtaout21.012.net.il ([80.179.55.169]:49971) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V04Lg-0001hh-Dl; Fri, 19 Jul 2013 02:39:28 -0400 Original-Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0MQ600H007TBDK00@a-mtaout21.012.net.il>; Fri, 19 Jul 2013 09:39:26 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MQ600H1U7TQDA10@a-mtaout21.012.net.il>; Fri, 19 Jul 2013 09:39:26 +0300 (IDT) In-reply-to: <87ip072t8d.fsf@catnip.gol.com> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.169 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:162008 Archived-At: > From: Miles Bader > Cc: Jan Dj=E4rv , emacs-devel@gnu.org > Date: Fri, 19 Jul 2013 11:12:18 +0900 >=20 > Eli Zaretskii writes: > >> What would those timers be for then? I can't find a single peri= odic > >> timer except blink timer that is on by default. > > > > Like I said, I firmly believe that most Emacs users have many def= aults > > overridden by customizations. Two popular timers that come to my= mind > > are display-time and jit-stealth. >=20 > 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 number= s up-to-date). > If jit-lock timers are firing too often, that could certainly be fi= xed > too, as there's nothing inherent about that which requires frequent= ly > firing timers when idle (or even when active, if all jit-locking ha= s > been completed and jit-lock'd buffers haven't changed)... >=20 > 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 Emac= s 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.