Symbol’s value as variable is void: lock-file-name-transforms

Symbol’s value as variable is void: lock-file-name-transforms

[tumashu]

[-- Attachment #1: Type: text/plain, Size: 301 bytes --]

Hello


     I have built the newest emacs from master branch, but have the below problem, how to deal with it ? thanks.



---------------------------------

feng@debian:~ $ ./emacs/emacs -Q

Symbol’s value as variable is void: lock-file-name-transforms
feng@debian:~ $
----------------------------

[-- Attachment #2: Type: text/html, Size: 509 bytes --]

Re: Symbol’s value as variable is void: lock-file-name-transforms

[Lars Ingebrigtsen]

tumashu <tumashu@163.com> writes:

> Symbol’s value as variable is void: lock-file-name-transforms

This is bug#49507, and we're discussing what to do about it.  I'm not
able to reproduce the problem myself, which doesn't help a lot with the
progress...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Re: Symbol’s value as variable is void: lock-file-name-transforms

[Eli Zaretskii]

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Fri, 16 Jul 2021 10:42:26 +0200
> Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
> 
> tumashu <tumashu@163.com> writes:
> 
> > Symbol’s value as variable is void: lock-file-name-transforms
> 
> This is bug#49507, and we're discussing what to do about it.

Why not remove the :initialize attribute from it?  I thought this was
agreed upon.

Re: Symbol’s value as variable is void: lock-file-name-transforms

[Lars Ingebrigtsen]

Eli Zaretskii <eliz@gnu.org> writes:

>> This is bug#49507, and we're discussing what to do about it.
>
> Why not remove the :initialize attribute from it?  I thought this was
> agreed upon.

I don't see why we should?  This problem can happen with any defcustom
with :initialize in it, I think?  (And we have a lot of those.)  So we
should fix the mechanism instead of altering the defcustom.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Re: Symbol’s value as variable is void: lock-file-name-transforms

[Eli Zaretskii]

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: tumashu@163.com,  emacs-devel@gnu.org
> Date: Fri, 16 Jul 2021 13:31:41 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> This is bug#49507, and we're discussing what to do about it.
> >
> > Why not remove the :initialize attribute from it?  I thought this was
> > agreed upon.
> 
> I don't see why we should?

Because there's no reason to use it in this case.

> This problem can happen with any defcustom with :initialize in it, I
> think?  (And we have a lot of those.)  So we should fix the
> mechanism instead of altering the defcustom.

I don't disagree, but I think we shouldn't wait with fixing the
specific issue with lock-file-name-transforms until the more general
issue is fixed.  That specific issue prevents people from building
Emacs, which is pretty serious.

Re: Symbol’s value as variable is void: lock-file-name-transforms

[Lars Ingebrigtsen]

Eli Zaretskii <eliz@gnu.org> writes:

> I don't disagree, but I think we shouldn't wait with fixing the
> specific issue with lock-file-name-transforms until the more general
> issue is fixed.  That specific issue prevents people from building
> Emacs, which is pretty serious.

Yeah, that's true.  I'll remove it and file a new bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Re: Symbol’s value as variable is void: lock-file-name-transforms

[Stefan Monnier]

Lars Ingebrigtsen [2021-07-16 13:31:41] wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>>> This is bug#49507, and we're discussing what to do about it.
>> Why not remove the :initialize attribute from it?  I thought this was
>> agreed upon.
> I don't see why we should?  This problem can happen with any defcustom
> with :initialize in it, I think?  (And we have a lot of those.)  So we
> should fix the mechanism instead of altering the defcustom.

I suspect that fixing the mechanism so that it can be used "reliably"
for any variable might prove very difficult.  So I think a better use of
our time is to keep using that feature as sparingly as possible.

[ Where "that feature" is `custom-initialize-delay` and not
  `:initialize`.  ]


        Stefan