From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Michael Albinus Newsgroups: gmane.emacs.bugs Subject: bug#49261: 28.0.50; File Locking Breaks Presumptuous Toolchains Date: Tue, 13 Jul 2021 19:53:24 +0200 Message-ID: <87h7gyaynf.fsf@gmx.de> References: <87v95mf2lj.fsf@gmx.de> <87pmvt3ob1.fsf@gnus.org> <87fswpgacv.fsf@gmx.de> <87bl7dfikj.fsf@gmx.de> <8735sofuqj.fsf@gmx.de> <83sg0oc83l.fsf@gnu.org> <87v95jevrm.fsf@gmx.de> <83lf6fdav4.fsf@gnu.org> <87r1g7eoor.fsf@gmx.de> <87im1jphyy.fsf@gnus.org> <87im1fd4fr.fsf@gmx.de> <83sg0jaaud.fsf@gnu.org> <87a6mrd2di.fsf@gmx.de> <838s2ba18y.fsf@gnu.org> <87pmvnsadx.fsf@gnus.org> <837dhva0vi.fsf@gnu.org> <871r83cszh.fsf@gmx.de> <834kcz9you.fsf@gnu.org> <87wnpvbc9q.fsf@gmx.de> <8335sj9ww7.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="404"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: larsi@gnus.org, ncaprisunfan@gmail.com, 49261@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jul 13 19:56:10 2021 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 1m3Mdd-000AYY-PM for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 13 Jul 2021 19:56:09 +0200 Original-Received: from localhost ([::1]:33404 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m3Mdc-0006MK-KK for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 13 Jul 2021 13:56:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59932) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m3Mba-00039p-8m for bug-gnu-emacs@gnu.org; Tue, 13 Jul 2021 13:54:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:58546) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1m3Mba-0006p8-0M for bug-gnu-emacs@gnu.org; Tue, 13 Jul 2021 13:54:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1m3MbZ-0003ka-Oh for bug-gnu-emacs@gnu.org; Tue, 13 Jul 2021 13:54:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Michael Albinus Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 13 Jul 2021 17:54:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 49261 X-GNU-PR-Package: emacs Original-Received: via spool by 49261-submit@debbugs.gnu.org id=B49261.162619881514372 (code B ref 49261); Tue, 13 Jul 2021 17:54:01 +0000 Original-Received: (at 49261) by debbugs.gnu.org; 13 Jul 2021 17:53:35 +0000 Original-Received: from localhost ([127.0.0.1]:41859 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1m3Mb8-0003jk-S1 for submit@debbugs.gnu.org; Tue, 13 Jul 2021 13:53:35 -0400 Original-Received: from mout.gmx.net ([212.227.17.21]:45409) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1m3Mb7-0003jV-8E for 49261@debbugs.gnu.org; Tue, 13 Jul 2021 13:53:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1626198806; bh=mx/SthyR7pF33jgDJrPlu9jtYj0E9NFvaJzx56oPWqI=; h=X-UI-Sender-Class:From:To:Cc:Subject:References:Date:In-Reply-To; b=l7sMRNOyclmCedCgwZzGYEkLHKIqiP2l32WS9wUFmht3Yz6PmoMjmKzo4W134daDI bN1EOUPcWv4kkmoOQoR5yCh5FmVswm8wlDLl2+10K2N/KKTWsMx70oj9W05LvOMaEX FMIHVday2e9K6I8w1ECxIyFig1XkW2I8fikkmpho= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from gandalf.gmx.de ([213.220.146.224]) by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1Mq2jC-1lQC602Che-00nCRp; Tue, 13 Jul 2021 19:53:26 +0200 In-Reply-To: <8335sj9ww7.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 12 Jul 2021 22:04:24 +0300") X-Provags-ID: V03:K1:CyID+tGlnaeyJ1AHrUY2juhbXxpd8qr9sUGM+PZzgPm3/rb+wkP IPesmTtbELa+P6VDQg2QT6dp49zCpp9tO9cqV52wp04JTis9hpiiKEwEfhqiiXC/dNWaCkB 6vs7w7GyGMiGu30NhCN6KX1lzFrKvk7Fjuo/U8e1bPC/w+CU8TTH+XcbMgwL/b5OMw50RIz ZkXMBtdWeiaxnCvC8zVKg== X-UI-Out-Filterresults: notjunk:1;V03:K0:MZBt4jG7oLo=:X3lg1329VokOhBULZ+iqZH nnxbIa8SHpveVw07HZEG3ElW/Tz+WmoHXd3BABd/LHxvHcMOfwbNfr+Diz5vtcS8gCrXtR12Z knK4qk/YlGe3VriC1qnm3rrswwbXdRi1ptUEiSpoNhwlvpoF6ay+Y0UiGz0NwPNddxc7VJjJ4 67FJUuowQY756uh+IuHhHyDrWDiQQa1+wc5W4KLCIDmU6RS1/bXuCgurbE6Mb4DKcLpFbAxRQ XMhes9q2zVff4w1TILHqTRXKAGboXPSoy34dqU3uO5q1AQZvr1jBJJMfreN5iAW1Yf8BdnH88 NyL6esfvJAAQ+kUvSMcUyYZPPKQ+XrpRuSGt9polw19icn4Z+AEd/jGYFoN9F+mWSozR2lvN4 1TNzOEazPWNwG3RBk3Vk97p/p4OuK6O/3X8jrlqftO8NdQYc1hASH2uuZpfFiCD6ew0juhAEw 9vt2lUEPc1czZKwwAQZZNDlphPKRQrNfIw88vurvJYZsPeWZuPQr5CdSh1CJJ2fKD9kfzuZAU WtMMbESaZi/5Jgw2OYHUKDF1sFPdODJR7t9GXonfUTDY7YB0bqS7HRZejq2DF7/1jfQAxjtbI xIHZnSTcxKnrrGDIc4fokiKx6Y8p8UikdmP8DS7ONG3XKnDGPaY2nlhIf9LZsDHIjFmMS42FC sIetgKpfbQZJPce47H8asTZFcoFk75W3Qjp5FHeOexZgegUq1apUFZgCiRhBc5niRpCQVg/2K Z7Iir4AMFg2Ls2XCZNCBY3+v6WVdIviJ/ghy1AytbsM9iC5n6jNut9Y+GoIGwsXAyQV9g/wT 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:209858 Archived-At: Eli Zaretskii writes: Hi Eli, >> >> 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: nobod= y(*) >> >> 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 i= t >> 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. Finally, I've added `remote-file-name-inhibit-locks'. The name shall look similar to the existing `remote-file-name-inhibit-cache'. Best regards, Michael.