From: Michael Albinus <michael.albinus@gmx.de>
To: Yuri D'Elia <wavexx@thregr.org>
Cc: 62614@debbugs.gnu.org
Subject: bug#62614: Tramp attempts to remove lock file with 'remote-file-name-inhibit-locks t
Date: Mon, 03 Apr 2023 11:54:08 +0200 [thread overview]
Message-ID: <87mt3pcmv3.fsf@gmx.de> (raw)
In-Reply-To: <874jpx1fn4.fsf@wavexx.thregr.org> (Yuri D'Elia's message of "Mon, 03 Apr 2023 11:19:19 +0200")
Yuri D'Elia <wavexx@thregr.org> writes:
Hi Yuri,
> 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?
Don't know, this behavior is "since ever" (I don't remember a change here).
With Tramp I'm agnostic. Tramp follows the behavior of local files. It
could do it differently, the local behavior could change, whatever.
Opinions?
>> One possible workaround for you would be to eval the following form,
>> additionally to your settings:
>>
>> (fset #'tramp-handle-unlock-file #'ignore)
>
> Looking at the definition of #'tramp-handle-unlock-file, it does
> actually look the most reasonable thing to do, but somehow having to
> fset an internal function doesn't feel right, but I don't have a better
> proposal since we don't have any setting that inhibit lock handling
> completely.
As said, it would be a workaround for your expectations. I won't
document it as global solution.
Best regards, Michael.
next prev parent reply other threads:[~2023-04-03 9:54 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 [this message]
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=87mt3pcmv3.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=62614@debbugs.gnu.org \
--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.