From: Dmitry Gutov <dmitry@gutov.dev>
To: 70900@debbugs.gnu.org
Subject: bug#70900: 30.0.50; tramp complains "File error: Cannot remove lock file for /ssh:..." on every save when remote-file-name-inhibit-locks is non-nil
Date: Mon, 13 May 2024 04:03:43 +0300 [thread overview]
Message-ID: <847791f3-e5ed-47d1-87b7-e6e95fb0b8d3@gutov.dev> (raw)
1. (setq remote-file-name-inhibit-locks t)
2. Open some file remotely, lightly edit and save it.
3. See this message in the Messages buffer.
BTW, I'm surprised this variable isn't mentioned in Tramp's FAQ (the
performance section in particular). It would also make sense to switch
it on by default - it has a noticeable effect on performance.
In GNU Emacs 30.0.50 (build 7, x86_64-pc-linux-gnu, X toolkit, cairo
version 1.18.0, Xaw scroll bars) of 2024-05-12 built on potemkin
Repository revision: b20d4ab374fb9b3c80b968df6acd6444f763bd40
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12302000
System Description: Ubuntu 23.10
next reply other threads:[~2024-05-13 1:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 1:03 Dmitry Gutov [this message]
2024-05-13 5:56 ` bug#70900: 30.0.50; tramp complains "File error: Cannot remove lock file for /ssh:..." on every save when remote-file-name-inhibit-locks is non-nil Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-13 6:54 ` Eli Zaretskii
2024-05-13 7:28 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-13 11:11 ` Dmitry Gutov
2024-05-15 10:20 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-13 11:30 ` Dmitry Gutov
2024-05-13 15:22 ` Eli Zaretskii
2024-05-13 22:31 ` Dmitry Gutov
2024-05-15 10:18 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-20 0:08 ` Dmitry Gutov
2024-05-13 11:30 ` Dmitry Gutov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=847791f3-e5ed-47d1-87b7-e6e95fb0b8d3@gutov.dev \
--to=dmitry@gutov.dev \
--cc=70900@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).