unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: xenodasein--- via "Emacs development discussions." <emacs-devel@gnu.org>
Cc: xenodasein@tutanota.de
Subject: Re: [External] : Re: Have Customize always use `custom-file`
Date: Tue, 04 Jan 2022 17:48:36 +0800	[thread overview]
Message-ID: <87sfu3bzm3.fsf@yahoo.com> (raw)
In-Reply-To: <MsZSolH--3-2@tutanota.de> (xenodasein's message of "Tue, 4 Jan 2022 10:41:45 +0100 (CET)")

xenodasein--- via "Emacs development discussions." <emacs-devel@gnu.org>
writes:

>> What Stefan M said was that you should not autoload variables, which is
>> advice not specific to custom whatsoever.
>>
>> Here is Stefan's entire reply for reference:
>>
>>  As a general rule, you don't want to autoload variables.
>>
>>  Yes, it's a known problem, and there's no really good solution to it
>>  (each solution I could come up with had its own set of
>>  bugs/misbehaviors), which is why all I can say is "don't autoload
>>  variables, please".
>>
>>  Even in the case where it happens to do what you want, it's
>>  undesirable in my experience. It just has too many quirks and corner
>>  cases
>>
>> Nowhere does he mention custom.

> What are you trying to say?

I'm trying to say that Stefan did not say that custom specifically has
problems with autoloaded variables in his reply on StackOverflow.

What he instead said was that variables should not be autoloaded.



  reply	other threads:[~2022-01-04  9:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 16:15 Have Customize always use `custom-file` Drew Adams
2022-01-03 16:20 ` xenodasein--- via Emacs development discussions.
2022-01-03 16:28   ` [External] : " Drew Adams
2022-01-03 17:02     ` xenodasein--- via Emacs development discussions.
2022-01-04  1:00       ` Po Lu
2022-01-04  9:41         ` xenodasein--- via Emacs development discussions.
2022-01-04  9:48           ` Po Lu [this message]
2022-01-04 10:29             ` xenodasein--- via Emacs development discussions.
2022-01-04 10:33               ` Po Lu
2022-01-04 10:44                 ` xenodasein--- via Emacs development discussions.
2022-01-04 10:53                   ` Po Lu
2022-01-05  3:54               ` Richard Stallman
2022-01-05  5:35                 ` tomas
2022-01-06  3:57                   ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sfu3bzm3.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=xenodasein@tutanota.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).