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: 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 12:42:49 -0400 [thread overview]
Message-ID: <jwvmtqs4y1a.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <838s2cc3ay.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 11 Jul 2021 17:50:45 +0300")
>> I don't see why being defined in C would be relevant, no.
> Because those are always defined when the startup code runs. By
> contrast, if you define them in some preloaded Lisp file, the
> defcustom form could run before the preloaded Lisp is restored from
> the pdumper file.
The error indeed came from the fact that the var is not defined when
`defcustom` is executed but instead only later on, when the predumped
Emacs is executed (in `startup.el`).
But to some extent it's only a side effect of the current implementation
of `custom-initialize-delay`. We could change it to also define the
variable when the `defcustom` is executed. [ AFAICT that should be
mostly painless, but past experience with this functionality tells me
that this change would inevitably introduce some unforeseen change
which we'd only discover a few months later ;-) ]
The underlying functionality is needed for any variable that's
predefined in the dump and yet whose default value can't be precomputed
when we dump Emacs. A `grep` shows that the vast majority of those
variables are defined in ELisp.
Stefan
next prev parent reply other threads:[~2021-07-11 16:42 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
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 [this message]
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=jwvmtqs4y1a.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).