GNU bug report logs - #49261
28.0.50; File Locking Breaks Presumptuous Toolchains

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: larsi <at> gnus.org, ncaprisunfan <at> gmail.com, 49261 <at> debbugs.gnu.org
Subject: bug#49261: 28.0.50; File Locking Breaks Presumptuous Toolchains
Date: Fri, 09 Jul 2021 13:45:19 +0300

> From: Michael Albinus <michael.albinus <at> gmx.de>
> Cc: larsi <at> gnus.org,  ncaprisunfan <at> gmail.com,  49261 <at> debbugs.gnu.org
> Date: Fri, 09 Jul 2021 10:28:29 +0200
> 
> > What other degrees besides "all" and "nothing" would you like to have?
> > And why?
> 
> Remote files (all files which match tramp-file-name-regexp). For
> backward compatibility, and possibly due to performance reasons.
> 
> Mounted files (all files which match `mounted-file-systems'). Possibly
> due to performance reasons.

You want a capability to exempt different kinds of files from locking?
Why would that be a good idea?  Performance doesn't cut it, IMO,
because if one wants to be protected from clobbering, one doesn't care
about performance.  And if one cares about performance for those
special kinds of files, it most probably means one doesn't care about
file locking at all.

So I submit that a binary switch is good enough.

> These are just examples. One could imagine more fine-grained choices
> (for example, only files located on a given host), or completely other
> selections.

I suggest not to imagine potential features.  We already have too many
features, so we should only add new ones if they are really required.
just because someone could use a finer-grained setting doesn't yet
mean we need to cater to that in core.

In any case, now that make-lock-file-name is exposed to Lisp, they can
override or advise it to do whatever they like, right?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.