From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
49507@debbugs.gnu.org, naofumi@yasufuku.dev
Subject: bug#49507: 28.0.50; macOS: Symbol’s value as variable is void: lock-file-name-transforms
Date: Sun, 11 Jul 2021 10:27:11 -0400 [thread overview]
Message-ID: <jwvsg0l3p8f.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83a6mtavas.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 11 Jul 2021 15:28:59 +0300")
> So I think we should simply remove the :initialize tag from that
> variable.
Agreed. `custom-initialize-delay` should be used sparingly.
> However, given this incident, I'm worried that others could trip on
> this subtlety. So I wonder whether we should describe it in the ELisp
> manual.
What is "it"? `custom-initialize-delay` is described in
`lispref/custom.texi` so are you suggesting that we don't describe
it there? I could go along with that (it's only meaningful for
predumped files so it is kind of "internal to Emacs's core").
At the same time I don't see how that would have helped here.
> I think we should generally advise against using this tag for
> defcustom's that might affect the startup code itself.
We should generally advise against using this initialization function
at all. Obviously it has its uses, but it's finicky.
> For 100% safety, one should probably use it only with variables
> defined in C. Stefan, do you agree?
I don't see why being defined in C would be relevant, no.
Stefan
next prev parent reply other threads:[~2021-07-11 14:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 17:11 bug#49507: 28.0.50; macOS: Symbol’s value as variable is void: lock-file-name-transforms Naofumi Yasufuku
2021-07-10 17:17 ` Lars Ingebrigtsen
2021-07-10 19:17 ` Naofumi Yasufuku
2021-07-10 19:29 ` Eli Zaretskii
2021-07-10 22:35 ` Naofumi Yasufuku
2021-07-11 6:22 ` Eli Zaretskii
2021-07-10 19:30 ` Lars Ingebrigtsen
2021-07-10 19:56 ` Lars Ingebrigtsen
2021-07-10 22:42 ` Naofumi Yasufuku
2021-07-11 6:21 ` Eli Zaretskii
2021-07-11 11:52 ` Lars Ingebrigtsen
2021-07-11 12:28 ` Eli Zaretskii
2021-07-11 14:27 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-07-11 14:50 ` Eli Zaretskii
2021-07-11 16:42 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-12 12:01 ` Lars Ingebrigtsen
2021-07-11 14:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-12 12:01 ` Lars Ingebrigtsen
2021-07-16 12:00 ` Lars Ingebrigtsen
2021-07-16 14:07 ` Naofumi Yasufuku
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=jwvsg0l3p8f.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=49507@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=naofumi@yasufuku.dev \
/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).