From: Yuri D'Elia <wavexx@thregr.org>
To: 62614@debbugs.gnu.org
Subject: bug#62614: Tramp attempts to remove lock file with 'remote-file-name-inhibit-locks t
Date: Sun, 02 Apr 2023 15:28:21 +0200 [thread overview]
Message-ID: <87pm8mv2ex.fsf@wavexx.thregr.org> (raw)
I have the following configuration to reduce remote latency while
saving, where the interesting tidbit is 'remote-file-name-inhibit-locks:
(setq tramp-ssh-controlmaster-options "-o ControlMaster=auto"
remote-file-name-inhibit-cache 300
remote-file-name-inhibit-locks t)
While editing a remote file via /scp:remote:test.txt I see the following
warning pop up:
Warning (unlock-file): Cannot remove lock file for /scp:remote:test.txt, ignored
because the lock file hasn't been created in the first place. I guess we
shouldn't attempt to unlock if there was no lock to begin with.
In GNU Emacs 30.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, cairo
version 1.16.0, Xaw scroll bars) of 2023-04-01 built on t14g2
Repository revision: 4bd1fc59664273c571aba8543940768c68eb336b
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12101007
System Description: Debian GNU/Linux 12 (bookworm)
Configured using:
'configure --with-x-toolkit=lucid --with-native-compilation
--with-tree-sitter --without-gsettings 'CFLAGS=-O3 -flto -march=native
-pipe ' 'LDFLAGS=-fuse-ld=mold -flto''
next reply other threads:[~2023-04-02 13:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 13:28 Yuri D'Elia [this message]
2023-04-03 8:35 ` bug#62614: Tramp attempts to remove lock file with 'remote-file-name-inhibit-locks t Michael Albinus
2023-04-03 9:19 ` Yuri D'Elia
2023-04-03 9:54 ` Michael Albinus
2023-04-03 10:01 ` Yuri D'Elia
2023-04-03 10:17 ` Yuri D'Elia
2023-04-03 10:30 ` Michael Albinus
2023-04-03 14:54 ` Yuri D'Elia
2023-04-03 16:32 ` Michael Albinus
2023-04-03 16:45 ` Eli Zaretskii
2023-04-03 18:50 ` Yuri D'Elia
2023-04-04 7:55 ` Michael Albinus
2023-04-03 14:14 ` Eli Zaretskii
2023-04-03 14:10 ` Eli Zaretskii
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=87pm8mv2ex.fsf@wavexx.thregr.org \
--to=wavexx@thregr.org \
--cc=62614@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 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.