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: Mon, 12 Jul 2021 22:04:24 +0300

> From: Michael Albinus <michael.albinus <at> gmx.de>
> Cc: larsi <at> gnus.org,  ncaprisunfan <at> gmail.com,  49261 <at> debbugs.gnu.org
> Date: Mon, 12 Jul 2021 20:46:57 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> > I suggested a compromise: disable it by default, but not via the
> >> > transform function.  I think it's more natural, but even if you
> >> > disagree, would it do as a compromise?
> >>
> >> I'm OK with another user option to disable it, it doesn't matter too
> >> much. But I'm not sure whether we shall disable it by default: nobody(*)
> >> will enable it ever, and all the effort would be wasted.
> >
> > Now _I_ am confused: didn't you say that we _should_ disable it by
> > default for remote files, because that was how Emacs worked until now?
> > Or what did I miss?
> 
> No. I meant we shall provide the *possibility* to disable it, because it
> didn't exist before.

Ah, okay.  I only said it should be disabled by default because I
thought that was what you suggested.  I have no problem whatsoever to
have remote locking enabled by default.

Previous Next

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