From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Blink Cursor mode is off by default Date: Tue, 12 Jun 2018 18:20:12 +0300 Message-ID: <83in6oowur.fsf@gnu.org> References: <838t7lqnf0.fsf@gnu.org> <83zi01p6th.fsf@gnu.org> <13a2189b89d06be494cbc21561713d5d.squirrel@dancol.org> <83o9ggpwfs.fsf@gnu.org> <98930BC3-F62C-4BFF-8B06-8CFB65E8D243@gnu.org> <5659356aea4cdccd07e28e441c1ae98b.squirrel@dancol.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1528816695 29378 195.159.176.226 (12 Jun 2018 15:18:15 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 12 Jun 2018 15:18:15 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: dancol@dancol.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 12 17:18:10 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fSl3i-0007W2-68 for ged-emacs-devel@m.gmane.org; Tue, 12 Jun 2018 17:18:10 +0200 Original-Received: from localhost ([::1]:56835 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fSl5n-0002yT-0O for ged-emacs-devel@m.gmane.org; Tue, 12 Jun 2018 11:20:19 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39207) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fSl5b-0002wL-WC for emacs-devel@gnu.org; Tue, 12 Jun 2018 11:20:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fSl5X-0006Mh-JE for emacs-devel@gnu.org; Tue, 12 Jun 2018 11:20:07 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:38526) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fSl5X-0006Mb-Eq; Tue, 12 Jun 2018 11:20:03 -0400 Original-Received: from [176.228.60.248] (port=3937 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fSl5W-0002H3-TZ; Tue, 12 Jun 2018 11:20:03 -0400 In-reply-to: <5659356aea4cdccd07e28e441c1ae98b.squirrel@dancol.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:226256 Archived-At: > Date: Mon, 11 Jun 2018 21:12:52 -0700 > From: dancol@dancol.org > Cc: "Daniel Colascione" , > monnier@iro.umontreal.ca, > emacs-devel@gnu.org > > > I think we can use (get var 'standard-value) instead to detect > > variables that were modified in early-init, and refrain from > > reinitializing them the second time. > > Does that work? In the case of (blink-cursor-mode -1), we just set > blink-cursor-mode to nil --- but it starts nil anyway, so we can't tell > the difference. The standard-value property doesn't help, I think. You are right: sadly, this doesn't work, certainly not when the user customization doesn't change the value that custom-reevaluate-setting sets. We have no infrastructure I could find that records anywhere the fact that user customizations changed did something, and in the specific case of a minor mode, custom-reevaluate-setting simply calls the mode function, so it does exactly what user customizations do. > > Clean, but unsafe, as important parts of startup has not yet > > been done. E.g., anything related to fonts or faces will probably > > not work reliably at that point. > > Works fine for me. We don't run early init _that_ early: it comes before > packages and site files, but the basic machinery is up. All I want is the > ability to configure the first frame before it appears, and only X > resources and early-init provide this ability. You are lucky, or maybe your customizations are sophisticated enough to work around the problems. Anyway, I consider the problem with failed initialization of cursor blinking serious enough to be in need of fixing. So I installed the second re-evaluation of custom-delayed-init-variables, and also added some blurb to the docs that advises against putting in the early init file what doesn't have to be there. I consider the problem with clobbering user customizations in early-init.el a secondary one, especially since we already do that with one or two variables anyway, although it would be good to fix that, of course.