From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: wavexx@thregr.org, 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 19:45:11 +0300 [thread overview]
Message-ID: <83fs9gvrs8.fsf@gnu.org> (raw)
In-Reply-To: <878rf90vvq.fsf@gmx.de> (message from Michael Albinus on Mon, 03 Apr 2023 18:32:25 +0200)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: Eli Zaretskii <eliz@gnu.org>, 62614@debbugs.gnu.org
> Date: Mon, 03 Apr 2023 18:32:25 +0200
>
> > On Mon, Apr 03 2023, Michael Albinus wrote:
> >>> IMHO if lock creation is inhibited, we could still attempt to remove the
> >>> lock to keep the old behavior, but then the warning shouldn't be
> >>> generated as you don't expect the lock to exist in the normal case.
> >>
> >> That might be an option. But it wouldn't fix your use case, where you
> >> try to avoid the file locking machinery for remote files at all.
> >
> > No, but it would fix an unexpected warning for both tramp and local
> > files, which I think is beneficial.
> >
> > On Mon, Apr 03 2023, Eli Zaretskii wrote:
> >> How about trying to remove the lock file, but if creation of lock
> >> files is disabled, suppressing the warning?
> >
> > As above.
>
> See appended patch.
LGTM, thanks.
> Shall it go to the emacs-29 or master branch?
Master, please.
next prev parent reply other threads:[~2023-04-03 16:45 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 [this message]
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=83fs9gvrs8.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.