From: Eli Zaretskii <eliz@gnu.org>
To: Yuri D'Elia <wavexx@thregr.org>
Cc: 62614@debbugs.gnu.org, michael.albinus@gmx.de
Subject: bug#62614: Tramp attempts to remove lock file with 'remote-file-name-inhibit-locks t
Date: Mon, 03 Apr 2023 17:10:26 +0300 [thread overview]
Message-ID: <83wn2tukdp.fsf@gnu.org> (raw)
In-Reply-To: <874jpx1fn4.fsf@wavexx.thregr.org> (message from Yuri D'Elia on Mon, 03 Apr 2023 11:19:19 +0200)
> Cc: 62614@debbugs.gnu.org
> From: Yuri D'Elia <wavexx@thregr.org>
> Date: Mon, 03 Apr 2023 11:19:19 +0200
>
> On Mon, Apr 03 2023, Michael Albinus wrote:
> > Tramp behaves like with local lock files. Imagine, you have a local file
> > ~/test with a lock file (a symbolic link) ~/.#test -> something. Set
> > create-lock-files to nil. Start editing the local file ~/test, and save
> > it. The local lock file ~/.#test is removed.
> >
> > And that's also what's documented, see (info "(elisp) File Locks")
> >
> > -- User Option: remote-file-name-inhibit-locks
> > You can prevent the creation of remote lock files by setting the
> > variable ‘remote-file-name-inhibit-locks’ to ‘t’.
> >
> >
> > It speaks only about creation of remote lock files, and not about
> > removal.
>
> Mmmh, maybe it should be mentioned explicitly. For me, "inhibit-locks"
> meant inhibiting both creation and removal.
>
> But even for local files, why the unlock is done? For cleanup?
Yes, because a lock file could be created before the option to avoid
them was set.
prev parent reply other threads:[~2023-04-03 14:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 13:28 bug#62614: Tramp attempts to remove lock file with 'remote-file-name-inhibit-locks t Yuri D'Elia
2023-04-03 8:35 ` 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 [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=83wn2tukdp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62614@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=wavexx@thregr.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.