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 03:45:50 -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> <83k3kky6l3.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1374392763 31622 80.91.229.3 (21 Jul 2013 07:46:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 21 Jul 2013 07:46:03 +0000 (UTC) Cc: miles@gnu.org, jan.h.d@swipnet.se, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jul 21 09:46:03 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 1V0oLC-0003mQ-Sp for ged-emacs-devel@m.gmane.org; Sun, 21 Jul 2013 09:46:03 +0200 Original-Received: from localhost ([::1]:60039 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V0oLC-00083w-D3 for ged-emacs-devel@m.gmane.org; Sun, 21 Jul 2013 03:46:02 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34718) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V0oL8-0007xH-9u for emacs-devel@gnu.org; Sun, 21 Jul 2013 03:46:00 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V0oL6-0004Zn-TB for emacs-devel@gnu.org; Sun, 21 Jul 2013 03:45:58 -0400 Original-Received: from chene.dit.umontreal.ca ([132.204.246.20]:52216) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V0oL5-0004Z9-2D; Sun, 21 Jul 2013 03:45:55 -0400 Original-Received: from fmsmemgm.homelinux.net (lechon.iro.umontreal.ca [132.204.27.242]) by chene.dit.umontreal.ca (8.14.1/8.14.1) with ESMTP id r6L7jpR4009757; Sun, 21 Jul 2013 03:45:52 -0400 Original-Received: by fmsmemgm.homelinux.net (Postfix, from userid 20848) id 67C6CAE0CA; Sun, 21 Jul 2013 03:45:50 -0400 (EDT) In-Reply-To: <83k3kky6l3.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 21 Jul 2013 05:44:56 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-NAI-Spam-Flag: NO X-NAI-Spam-Threshold: 5 X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 1 Rules triggered RV4645=0 X-NAI-Spam-Version: 2.3.0.9362 : core <4645> : streams <1003880> : uri <1482752> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 132.204.246.20 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:162047 Archived-At: >> No, indeed, but they're not activated unless the user asks for >> it explicitly. > I don't see how this is relevant. It's relevant because most optional features are turned off. > Are we going to tell users not to enable features if they want Emacs > to be friendly to the batteries? That's not going to happen. jit-lock-stealth is pretty clearly battery unfriendly. It's in its nature. >> 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. > JIT Stealth has a variable to limit the system load it imposes; mine > is set to 20%. Yes, we did try to make jit-lock-stealth work acceptably, but after many attempts, we chose to turn it off instead because there's always some situation where it consumes a lot more CPU than what you'd want. Stefan