From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Blink cursor changes, possible W32 breakage. Date: Sun, 21 Jul 2013 22:55:25 -0400 Message-ID: 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> <83vc46zwsy.fsf@gnu.org> <83zjthy438.fsf@gnu.org> <51EBA7DE.8090105@gmx.at> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1374461732 28042 80.91.229.3 (22 Jul 2013 02:55:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 22 Jul 2013 02:55:32 +0000 (UTC) Cc: Eli Zaretskii , jan.h.d@swipnet.se, emacs-devel@gnu.org, miles@gnu.org To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jul 22 04:55:32 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 1V16Hb-00047I-J0 for ged-emacs-devel@m.gmane.org; Mon, 22 Jul 2013 04:55:31 +0200 Original-Received: from localhost ([::1]:55914 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V16Hb-00004v-9Z for ged-emacs-devel@m.gmane.org; Sun, 21 Jul 2013 22:55:31 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58329) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V16HY-0008WI-R4 for emacs-devel@gnu.org; Sun, 21 Jul 2013 22:55:29 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V16HX-0002iN-PV for emacs-devel@gnu.org; Sun, 21 Jul 2013 22:55:28 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:59323) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V16HW-0002iB-Ck; Sun, 21 Jul 2013 22:55:26 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EABK/CFG4rw7r/2dsb2JhbABEvw4Xc4IeAQEEAVYjEAs0EhQYDSSIHgbBLZEKA6R6gV6DEw X-IPAS-Result: Av4EABK/CFG4rw7r/2dsb2JhbABEvw4Xc4IeAQEEAVYjEAs0EhQYDSSIHgbBLZEKA6R6gV6DEw X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="19475303" Original-Received: from 184-175-14-235.dsl.teksavvy.com (HELO fmsmemgm.homelinux.net) ([184.175.14.235]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 21 Jul 2013 22:55:19 -0400 Original-Received: by fmsmemgm.homelinux.net (Postfix, from userid 20848) id 2AA46AE1D1; Sun, 21 Jul 2013 22:55:25 -0400 (EDT) In-Reply-To: <51EBA7DE.8090105@gmx.at> (martin rudalics's message of "Sun, 21 Jul 2013 11:20:30 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.182 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:162063 Archived-At: >> ... they're not activated unless the user asks for >> it explicitly. > `jit-lock-context-timer' is activated here though I never asked for it > "explicitly". Indeed context refontification is enabled by default, but that's only an idle timer, so it shouldn't keep firing repeatedly while Emacs is idle. >> Also jit-lock-stealth used to be enabled by default but >> was disabled because too many people found it problematic, so only those >> people who don't care about high/excessive background CPU usage will >> have it enabled. > I'm too silly to understand: Don't we talk about the case where Emacs > remains idle? Shouldn't these timers trigger once only after that > happened? No, the jit-lock-stealth code keeps on running for a potentially long time after Emacs became idle (IIRC it uses a while-input-pending-p kind of loop). But yes, the timer only triggers once. Stefan