From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "Jay Berkenbilt" Newsgroups: gmane.emacs.bugs Subject: bug#53207: 28.0.91; create-lockfiles nil breaks file change detection Date: Wed, 12 Jan 2022 15:07:32 -0500 Message-ID: <3759fdad-fb95-4af8-b2bf-146abb81eb3d@www.fastmail.com> References: <509ddd0f-589c-45b0-9b60-5820f4c1d716@www.fastmail.com> <83bl0g6f29.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32605"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Cyrus-JMAP/3.5.0-alpha0-4569-g891f756243-fm-20220111.001-g891f7562 Cc: 53207@debbugs.gnu.org To: "Eli Zaretskii" Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Jan 12 21:09:15 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n7jvl-0008Ds-3I for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 12 Jan 2022 21:09:13 +0100 Original-Received: from localhost ([::1]:53826 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n7jvj-0001DC-IB for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 12 Jan 2022 15:09:11 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:39016) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n7jvd-0001D0-A8 for bug-gnu-emacs@gnu.org; Wed, 12 Jan 2022 15:09:05 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:38093) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1n7jva-0000Cs-2k for bug-gnu-emacs@gnu.org; Wed, 12 Jan 2022 15:09:04 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1n7jvZ-00057B-TK for bug-gnu-emacs@gnu.org; Wed, 12 Jan 2022 15:09:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: "Jay Berkenbilt" Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 12 Jan 2022 20:09:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 53207 X-GNU-PR-Package: emacs Original-Received: via spool by 53207-submit@debbugs.gnu.org id=B53207.164201809019586 (code B ref 53207); Wed, 12 Jan 2022 20:09:01 +0000 Original-Received: (at 53207) by debbugs.gnu.org; 12 Jan 2022 20:08:10 +0000 Original-Received: from localhost ([127.0.0.1]:59229 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n7jui-00055p-9P for submit@debbugs.gnu.org; Wed, 12 Jan 2022 15:08:09 -0500 Original-Received: from out2-smtp.messagingengine.com ([66.111.4.26]:34491) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n7juc-00055G-Qs for 53207@debbugs.gnu.org; Wed, 12 Jan 2022 15:08:06 -0500 Original-Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id C10725C01D1; Wed, 12 Jan 2022 15:07:57 -0500 (EST) Original-Received: from imap49 ([10.202.2.99]) by compute1.internal (MEProxy); Wed, 12 Jan 2022 15:07:57 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ql.org; h= mime-version:message-id:in-reply-to:references:date:from:to:cc :subject:content-type; s=fm3; bh=zbkQ/BR2f0jAV2c5kfAoE7wEghSeg2A KGJO3HohNQXI=; b=CApLDzXecAJpNDMQkUjFSPYaMpK3Eprg9jpQ0cA3Pewlk/O XE7BBmDqM9bujfE62vbgkyXLkJ/1kG6Y7nmxkOezgKJfaZ0f0GId+DId0OuBes3m r98Jzf5+YAR2yR8GOSF4aMMjAVL8njL87WNjIvso4sDGTGXviq0f6L5NTf/RK8S/ GglNOdVvhh/O1D+EiIRLgpeGcTzDL6Xiuna8O961KjApg27muPLc2myArRF6GKxc zTQC8syRtZX/penPQ1OOXfCY7anutibBGQ6okagCnOqbgTuBtn/2l39ppXTfbdii Mnj6I52rf2VKemylBFLutwcmtiOBlgXuwZq8A1g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=zbkQ/B R2f0jAV2c5kfAoE7wEghSeg2AKGJO3HohNQXI=; b=UmZVZ3fN187lWVzQNTvXtv C3VTl6OX9Q19EzB1YqdayEeGL0CGmSHS/N1Ge8SDGfgTu2TiEVu59plMV50pVHgX dHAg95gKeG9r4YjgZTwg2nbNDfHzAxsYx/E0zoTvlEm7MAutO/soEOfdo5aaa5Kb EqBVo9akiQTQ2XmDm0Kv42cBdJBa996lL4mJZaLN5bQCYTE1qKvwiwm0X8HER6QJ YaBP43Ldu4l3jfScHWCLmNNJkDmfXm2Yh4nd9jPdLiFYR/1EI2wQlGj1ZEb38Wv0 Y+2SATcCC9gXpo4oMQj2iqbWkGZhZEOcXXhlsjFq+9sSnDXohglaDJoW1D7t9AGw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrtddugddutdekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreertdenucfhrhhomhepfdflrgih uceuvghrkhgvnhgsihhlthdfuceovghjsgesqhhlrdhorhhgqeenucggtffrrghtthgvrh hnpeehtdevhfefvdffgfeifeduheefhfduhfegfffgffdtveelffehvddvheejffeukeen ucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegvjhgsse hqlhdrohhrgh X-ME-Proxy: Original-Received: by mailuser.nyi.internal (Postfix, from userid 501) id 6B49FF60075; Wed, 12 Jan 2022 15:07:57 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface In-Reply-To: <83bl0g6f29.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:224041 Archived-At: On Wed, Jan 12, 2022, at 12:26 PM, Eli Zaretskii wrote: > > Date: Wed, 12 Jan 2022 09:30:07 -0500 > > From: "Jay Berkenbilt" > > > > Bottom line: in emacs 27.2, setting create-lockfiles to nil does not change the behavior. In emacs 28.0.91, it does. I also noticed this in 28.0.90 but hadn't had time to figure out how to reproduce it without my customizations. > > You seem to assume that create-lockfiles is _only_ about the creation > of the lockfiles. But that's not true: the variable is a misnomer, > and it actually controls the entire functionality of preventing > editing collisions. Including the test for the file being modified > behind Emacs's back. The doc string says: > > Non-nil means use lockfiles to avoid editing collisions. I interpreted this to mean that this was the method of preventing collisions, as opposed to some other method. > > > Is this change intentional? If so, can I configure something to go > > back to the old behavior? > > My suggestion is to stop setting create-lockfiles to a nil value. Why > is the non-nil value a problem? Emacs lockfiles are dangling symbolic links. Some tools and systems don't like those. For example, I was working on a learning project to teach myself modern web development and was using tools that do hot reload, scanning directories for tests. Every time I started editing, it would pick up the lock file and give an error. You could make an argument that it is a bug in the tool, but the cross section of people who live and breathe in emacs and who are working on front-end web development seems to be very small, and there's little incentive for them to add code that ignores dangling symbolic links. Most people consider those to be errors. I get why it's done though -- I have implemented symlink-based lock files myself since they are easier to make atomic, especially when network file systems are in play. But, from a pragmatic standpoint, I don't need them, and I'd like to turn them off, and it used to work and no longer does. This is why I'm testing 28 -- to catch things like this.