From: Dmitry Gutov <dmitry@gutov.dev>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 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 14:30:18 +0300 [thread overview]
Message-ID: <5235ea0a-5481-4490-8e09-6ceada5e08bb@gutov.dev> (raw)
In-Reply-To: <87r0e6gsqa.fsf@gmx.de>
On 13/05/2024 08:56, Michael Albinus wrote:
>> BTW, I'm surprised this variable isn't mentioned in Tramp's FAQ (the
>> performance section in particular).
> ???
>
> In the Tramp manual, node "Frequently Asked Questions", item "How to
> speed up TRAMP?", there is
>
> --8<---------------cut here---------------start------------->8---
> − Disable file locks. Set ‘remote-file-name-inhibit-locks’ to
> ‘t’ if you know that different Emacs sessions are not
> modifying the same remote file.
> --8<---------------cut here---------------end--------------->8---
Yes, sorry, I see it now.
prev parent reply other threads:[~2024-05-13 11:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 1:03 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 Dmitry Gutov
2024-05-13 5:56 ` 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5235ea0a-5481-4490-8e09-6ceada5e08bb@gutov.dev \
--to=dmitry@gutov.dev \
--cc=70900@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.