From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Tim Cross Newsgroups: gmane.emacs.devel Subject: Re: [External] : Re: Default custom file was: Re: Propose to add setup-wizard.el to ELPA Date: Fri, 07 Jan 2022 07:11:30 +1100 Message-ID: <871r1k38ym.fsf@gmail.com> References: <740A136F-8710-4F4C-BFC1-A3DB418447F4@gmail.com> <87zgoc7u6k.fsf@gmail.com> <83iluzbqcr.fsf@gnu.org> <87r19nxx7x.fsf@gmail.com> <878rvv9esx.fsf@yahoo.com> <87fsq28x4l.fsf@yahoo.com> <87bl0q8vfa.fsf@yahoo.com> <83pmp69vsu.fsf@gnu.org> <8735m17l8c.fsf@yahoo.com> <875yqx5nub.fsf@yahoo.com> <83lezt8cm6.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32742"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.7.5; emacs 28.0.90 To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jan 06 21:29:17 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n5ZNs-0008HL-Sp for ged-emacs-devel@m.gmane-mx.org; Thu, 06 Jan 2022 21:29:16 +0100 Original-Received: from localhost ([::1]:57216 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n5ZNq-0000D2-Mx for ged-emacs-devel@m.gmane-mx.org; Thu, 06 Jan 2022 15:29:14 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:58774) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n5ZN1-0007nx-SU for emacs-devel@gnu.org; Thu, 06 Jan 2022 15:28:23 -0500 Original-Received: from [2607:f8b0:4864:20::1032] (port=51018 helo=mail-pj1-x1032.google.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1n5ZN0-0002XP-Cf for emacs-devel@gnu.org; Thu, 06 Jan 2022 15:28:23 -0500 Original-Received: by mail-pj1-x1032.google.com with SMTP id gp5so3448223pjb.0 for ; Thu, 06 Jan 2022 12:28:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=references:user-agent:from:to:subject:date:in-reply-to:message-id :mime-version; bh=pbvM6ZuBpQcYmyhcljz3bHRccB29wy4/HRZPJkTRu3E=; b=XoSceIPU1z5bUG+eAJMo4Q/4BWYu6ZT7+HuahcESvz63aqBaEh25GbcGF1s17xReMp xmqTNV8iUTF9gMERovHCF8CCyiwdIOMtAV3YGj44hmkcDm5+5cRHRcDnKDG9Uw/mMlip cJ3KvHws6gcq9dkpBhDwQFSo2voyZE0Fq6i25kjtXaeNl8M3jbGI7aYdwM2lBIZad4f0 EL7sKLmLzRKkIvHZNJOpG8OwVePUmZ5SMQTmOu6KV/wzxgJbr9TxioljSjbHCPcGRufw TILbW3EnE4nqlsBGWvHmuHDhHUkl4fzOrZx+pA6QGc2/bpX4KTgpx3+4yCKU9IswWOaP xOTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:references:user-agent:from:to:subject:date :in-reply-to:message-id:mime-version; bh=pbvM6ZuBpQcYmyhcljz3bHRccB29wy4/HRZPJkTRu3E=; b=i+un7TMtkhkKy9hPbtedYEGE/w/m7hYOv2g6Lps0ntyVkRuwTunfzhXb9tu2y6d4Qk r9rRS8pkkNf5mNo38q2H5lbh/07ngFY//eMQ2lNperpubReoz3po1gtaBmDWl8yZtERJ 1YNGK7T49j8wsxhunvJrx0i45Voal6N7FMlL4Xhyyln/j0yt/tsi0T6sr3vek/tI5ydp 1Ms49F27N5vU+Rng+5DDTbrofBEfmVWA31F2FTcAgiXCaSYq0Ahfo5GLY0tog/afZWFc YSsXx5jp7z1AE7stTujTJ4Pxi2jQGu0C751f/4nfYYe6bBu9/t3rmN2kgl+1ElzmS7pw KhYQ== X-Gm-Message-State: AOAM5305OQCeZ6JhJp5B9cdJTvGwwwJLdvZjqD55Ho64ury/7TtONiQo 4ZveHg5ebNe80tSaE8XJyzxNiCTkQhY= X-Google-Smtp-Source: ABdhPJz6/CRmNgLaE0XaPVm3CuDmoM8OuM5B+ynVhAId4rkNBNVrJ8I+1ZjvpWa1T4p+RYm43s3IAg== X-Received: by 2002:a17:90a:5d16:: with SMTP id s22mr11996273pji.81.1641500900824; Thu, 06 Jan 2022 12:28:20 -0800 (PST) Original-Received: from dingbat ([124.149.107.194]) by smtp.gmail.com with ESMTPSA id h19sm3401889pfh.30.2022.01.06.12.28.19 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 06 Jan 2022 12:28:20 -0800 (PST) In-reply-to: X-Host-Lookup-Failed: Reverse DNS lookup failed for 2607:f8b0:4864:20::1032 (failed) Received-SPF: pass client-ip=2607:f8b0:4864:20::1032; envelope-from=theophilusx@gmail.com; helo=mail-pj1-x1032.google.com X-Spam_score_int: -12 X-Spam_score: -1.3 X-Spam_bar: - X-Spam_report: (-1.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:284346 Archived-At: Drew Adams writes: > > And what if there's a `custom-set-variables', > `customize-set-variable', `customize-set-value', > `custom-save-variables', customize-save-variable, > `customize-save-all', `custom-save-all', > `custom-save-faces', `customize-save-customized', > or `customize-saved' in the init file? > > What if such is not in the init file but in > some file that's loaded by the init file? > > What if such files get loaded conditionally? > Are you going to analyze the code and then > search through all the possible source code > for occurrences? What if some such code is > generated? I think this is one of the more important and easily overlooked issue raised in this thread. I've noticed in recent times a growing use of the various customise functions in a programatic manner within user initialisation code. Such code is often spread across multiple files which are loaded by the user's init file at startup. For this issue, I do have to put myself in the very conservative camp. I'm not convinced we have a real issue here and may be either creating problems that are more theoretical than actual or guilty of premature optimisations. For new users, I don't think there are any real issues with the existing situation. Most of the issues raised seem to be more issues that arise once the user has become more experienced and wants to delve deeper into their Emacs configuration. By that point, they will typically have the skills to use the existing facilities to break off the custom data into its own file and load it at whatever point is appropriate for their style of configuration. I fear that if we try to make the Emacs startup process 'smarter', we are likely to actually make it more frustrating for those who like to have fine grained control and unnoticeable by those who don't care. In the end, all we get is more complexity wiht little improved functionality.