Subject: bug#49261: 28.0.50; File Locking Breaks Presumptuous Toolchains

From: Eli Zaretskii <[email-masked]>
Date: Wed, 07 Jul 2021 21:50:38 +0300

> From: Lars Ingebrigtsen <[email-masked]>
> Cc: [email-masked],  [email-masked],  [email-masked]
> Date: Wed, 07 Jul 2021 20:17:22 +0200
> 
> Hm...  I think for simplicity's sake, it makes sense to always call the
> Lisp code.  Having two places where we insert ".#" into a file name just
> seems error prone, long term.

Btw, we could avoid having 2 places that produces the default
".#"+FILENAME lock file name by exposing to Lisp a C primitive which
does that.  So that problem can easily be solved.