unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Naofumi Yasufuku <naofumi@yasufuku.dev>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 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 07:42:15 +0900	[thread overview]
Message-ID: <m1y2adyens.fsf@yasufuku.dev> (raw)
In-Reply-To: <87h7h2lz7w.fsf@gnus.org>


Lars Ingebrigtsen <larsi@gnus.org> writes:

> Naofumi Yasufuku <naofumi@yasufuku.dev> writes:
>
>> Precondition:
>> - Repository revision: 9ce6541ac9710933beca7f9944087fe4849d5ae9
>> - macOS
>> - $ mv ~/.emacs.d/eln-cache ~/.emacs.d/eln-cache.old
>>
>> Emacs doesn't start due to the following error:
>>   $ ./src/emacs -Q
>>   Symbol’s value as variable is void: lock-file-name-transforms
>>   $
>
> [...]
>
>> -  return call1 (Qmake_lock_file_name, Fexpand_file_name (fn, Qnil));
>> +  Lisp_Object func = intern ("make-lock-file-name");
>> +  if (NILP (Fboundp (func)))
>> +    return Qnil;
>> +  return call1 (func, Fexpand_file_name (fn, Qnil));
>
> Well, that code was buggy (as Michael pointed out) -- Fboundp doesn't
> work on interned symbols, apparently?
>
> But in any case, make-lock-file-name and lock-file-name-transforms are
> defined in the same file ("files.el"), so what you're seeing here just
> shouldn't be possible -- it should complain about make-lock-file-name
> being undefined, not the variable.
>

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")
 
 (defvar auto-save--timer nil "Timer for `auto-save-visited-mode'.")
----


> So I think this points to there being something odd going on in your
> build tree.  Are you sure you have no private modifications in the tree?
> Do you still see this issue from a freshly checked out tree?

I've tested with fresh build of new checked out under both macOS and
linux (Ubuntu 21.04).  The result is same.





  reply	other threads:[~2021-07-10 22: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 [this message]
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
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=m1y2adyens.fsf@yasufuku.dev \
    --to=naofumi@yasufuku.dev \
    --cc=49507@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /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).