From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pedro Andres Aranda Gutierrez Newsgroups: gmane.emacs.devel Subject: Re: [External] : Re: Default custom file was: Re: Propose to add setup-wizard.el to ELPA Date: Wed, 5 Jan 2022 10:58:10 +0100 Message-ID: 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> <8735m28qzr.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000002e52a905d4d2cc36" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21555"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Robert Pluim , "emacs-devel@gnu.org" , Stefan Kangas , Eli Zaretskii , Drew Adams To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jan 05 11:02:31 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 1n537n-0005Ne-AA for ged-emacs-devel@m.gmane-mx.org; Wed, 05 Jan 2022 11:02:31 +0100 Original-Received: from localhost ([::1]:51002 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n537m-0006XX-2j for ged-emacs-devel@m.gmane-mx.org; Wed, 05 Jan 2022 05:02:30 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:57274) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n534C-0004du-QW for emacs-devel@gnu.org; Wed, 05 Jan 2022 04:58:53 -0500 Original-Received: from [2a00:1450:4864:20::52f] (port=42865 helo=mail-ed1-x52f.google.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1n5346-0004eC-Dk; Wed, 05 Jan 2022 04:58:45 -0500 Original-Received: by mail-ed1-x52f.google.com with SMTP id j21so159596901edt.9; Wed, 05 Jan 2022 01:58:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=vu0u/acY3Sit9m6+kHMl2QqzHnWkktDVHeBu3YVOAJs=; b=Id5gRqsIY6OwKma72/ySJLInfBHKwNzBQDNepLCsvsX8hnf3b4xuhhdONVb9BmEvtN 9XDjLPrT+ANkN6CU9ct+X01qYjW3ZZAgwP6+JTd0ty2ajxK5acUf9/HxaWYiNucyYZVG oIu808/d/ChgAd6WiPQHOPiQ8VX2gQ6AEIZR8pN8P0J0J24PCQaL8cY1BLRpwjf3SkqJ A5tfSVcyFTwion2xriutk5YxfqHz3nUFVGb8uk/BLxe8NWSERyq6C3/c86H58686hjK7 RE7dKNGY8xwCGN2eDcr5URDvScIjptrZrrqkH60hxp8UgtOuGDt7g958fTPhmK0kn+EH E8jw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=vu0u/acY3Sit9m6+kHMl2QqzHnWkktDVHeBu3YVOAJs=; b=ijaCUJm/ISepVmQOl3QEm73iCWQRzO+Rk/J0rXw7q5zKAnOCugWu0goO4Rhkh6b6cs nT9SHwxbcNJLWcZgH/hhC3obdvHyvluWKMeksKaJOjb5VoK+J+tUP6liTzXh4PRyFp80 w77UEWBzvytQn6fFSrusNLNWx1cJbFBepwGeKr77/7gK3scUB3SMl8tc0gSaJ+LSQU14 DMJSqA04uyDKHmie1Qwed89r7TD8dr3acpvYBwELfJb6vXHM8uYA/1Ysdj5n/nT2EFVz gv1QLMIWbXgyXKTGmr1egTnSr0rHiXuxACef38syCs1MBmVtlUGoQ8frHVHbCeYHw/NP YgQQ== X-Gm-Message-State: AOAM532vtVnIhVv05UlcfWQWzKAf5ah9H/86+C6TvWX3jESA0pkkknMv SpZ/nd2BEb/7/XfrsA8ZZdCtjXKiMARGIeinHk4= X-Google-Smtp-Source: ABdhPJx4I81M7VEYcXEATcpUbGRiPRuVI3HVzCdcHDXFJZYTa/sUxktLl0rCzXDvBl1gVRHMajSNnZFHALlNDvl85jk= X-Received: by 2002:a05:6402:348b:: with SMTP id v11mr48310744edc.309.1641376717360; Wed, 05 Jan 2022 01:58:37 -0800 (PST) In-Reply-To: <8735m28qzr.fsf@yahoo.com> X-Host-Lookup-Failed: Reverse DNS lookup failed for 2a00:1450:4864:20::52f (failed) Received-SPF: pass client-ip=2a00:1450:4864:20::52f; envelope-from=paaguti@gmail.com; helo=mail-ed1-x52f.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, HTML_MESSAGE=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:284227 Archived-At: --0000000000002e52a905d4d2cc36 Content-Type: text/plain; charset="UTF-8" OK, lots of things to react to. > Not defining `custom-file' _would_ change the > behavior. Setting `custom-file' to your init > file would keep the current default behavior of > Customize using your init file. IMHO, that's a bit more disruptive (Po Lu, you made me think about that ;-) )... And using the NEWS to explain the change might have people getting mad. My approach, as detailed above. might be less "aggressive", right? Wouldn't be people happier with it? Like in "I didn't say anything about custom-file, so if I don't, nothing changes" Then they can eventually set custom-file to "~/.emacs.d/custom.el" to migrate (NEWS might be a nice place to advertise this) With that I'd be more than happy, because I would be able to define my OS specific custom-file and have it loaded. > Why byte-compile your init file? That was something I wasn't thinking about. I never byte-compiled my init file, nor would I think that custom-file should be byte-compiled either :-) /PA On Wed, 5 Jan 2022 at 10:35, Po Lu wrote: > LdBeth writes: > > > I think saving custom set variables to init file somehow prevents > > using byte compiled init.el file effectively (unless the user hooks > > auto compile whenever it is changed by emacs). From that perspective, > > I'm happy to see that this behavior is to be changed. > > Why byte-compile your init file? It usually makes no measurable > difference whatsoever, except it breaks things like custom-set-variables > and inhibit-startup-echo-area-message. > > Thanks. > -- Fragen sind nicht da um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler --0000000000002e52a905d4d2cc36 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
OK, lots of things to react to.

<= div>> Not defining `custom-file' _would_ change the
> behavior.=C2=A0 Setting `custom-file' to your init
> file would keep the current default behavior of
> Customize usin= g your init file.

IMHO, that's a bit more= disruptive (Po Lu, you made me think about that ;-) )...
And us= ing the NEWS to explain the change might have people getting mad.

My approach, as detailed above. might be less "aggress= ive", right? Wouldn't be people happier with it?
Like in= "I didn't say anything about custom-file, so if I don't, noth= ing changes"
Then they can eventually set custom-file t= o "~/.emacs.d/custom.el" to migrate (NEWS might be a nice place t= o advertise this)

With that I'd be more than h= appy, because I would be able to define my OS specific custom-file and have= it loaded.

> Why byte-compile your init fi= le?
That was something I wasn't thinking about. I never byte-= compiled my init file, nor would I think that custom-file should be byte-co= mpiled either :-)

/PA

On Wed, 5 Jan 2022 = at 10:35, Po Lu <luangruo@yahoo.co= m> wrote:
LdBeth <andpuk= e@foxmail.com> writes:

> I think saving custom set variables to init file somehow prevents
> using byte compiled init.el file effectively (unless the user hooks > auto compile whenever it is changed by emacs). From that perspective,<= br> > I'm happy to see that this behavior is to be changed.

Why byte-compile your init file?=C2=A0 It usually makes no measurable
difference whatsoever, except it breaks things like custom-set-variables and inhibit-startup-echo-area-message.

Thanks.


--
Fragen sin= d nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu= werden
Georg Kreisler
--0000000000002e52a905d4d2cc36--