From: Eli Zaretskii <eliz@gnu.org>
To: Naofumi Yasufuku <naofumi@yasufuku.dev>
Cc: larsi@gnus.org, 49507@debbugs.gnu.org
Subject: bug#49507: 28.0.50; macOS: Symbol’s value as variable is void: lock-file-name-transforms
Date: Sun, 11 Jul 2021 09:21:23 +0300 [thread overview]
Message-ID: <83im1hbcbg.fsf@gnu.org> (raw)
In-Reply-To: <m1y2adyens.fsf@yasufuku.dev> (message from Naofumi Yasufuku on Sun, 11 Jul 2021 07:42:15 +0900)
> From: Naofumi Yasufuku <naofumi@yasufuku.dev>
> Date: Sun, 11 Jul 2021 07:42:15 +0900
> Cc: 49507@debbugs.gnu.org
>
> I found that the following simple `lock-file-name-transforms' change
> can also avoid this error:
>
> ----
> lisp/files.el | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/lisp/files.el b/lisp/files.el
> index 0dfcab8f89..894a06e6e7 100644
> --- a/lisp/files.el
> +++ b/lisp/files.el
> @@ -424,7 +424,6 @@ lock-file-name-transforms
> :type '(repeat (list (regexp :tag "Regexp")
> (string :tag "Replacement")
> (boolean :tag "Uniquify")))
> - :initialize 'custom-initialize-delay
> :version "28.1")
Ah, I see the problem. Defcustom's that are marked with
'custom-initialize-delay are evaluated early in the process of
restoring from the pdumper file, when the code of files.el was not yet
loaded.
Lars, why did you use this :initialize tag here?
next prev parent reply other threads:[~2021-07-11 6:21 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 [this message]
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
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=83im1hbcbg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=49507@debbugs.gnu.org \
--cc=larsi@gnus.org \
--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).