all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Duncan Greatwood <dgreatwood@gmail.com>
Cc: 70973-done@debbugs.gnu.org
Subject: bug#70973: 29.1; "Unlocking file: Invalid argument" Warning saving via a softlink with stale file lock
Date: Sat, 01 Jun 2024 17:04:29 +0300	[thread overview]
Message-ID: <86wmn8oj2q.fsf@gnu.org> (raw)
In-Reply-To: <CAGg=3NVstcd_hE3N5VNjj30uFN8hBEqDXPaTK-_v737hQ5L03g@mail.gmail.com> (message from Duncan Greatwood on Thu, 16 May 2024 14:36:37 -0700)

> From: Duncan Greatwood <dgreatwood@gmail.com>
> Date: Thu, 16 May 2024 14:36:37 -0700
> Cc: 70973@debbugs.gnu.org
> 
> I would agree that the issue was likely due to a system crash at an inopportune moment.
> 
> Of course, if emacs did detect a bad lock file, it could prompt the user for confirmation before removing /
> replacing it. No need to be silent.
> 
> The status quo, requiring a user to find and remove the lock file manually, seems burdensome to my eye,
> albeit the issue is presumably rare. But certainly it is a matter of taste.

No further comments, so I'm now closing this bug.





      reply	other threads:[~2024-06-01 14:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16  0:53 bug#70973: 29.1; "Unlocking file: Invalid argument" Warning saving via a softlink with stale file lock Duncan Greatwood
2024-05-16  8:43 ` Eli Zaretskii
2024-05-16 14:17   ` Duncan Greatwood
2024-05-16 15:46     ` Eli Zaretskii
2024-05-16 15:55       ` Duncan Greatwood
2024-05-16 16:09         ` Eli Zaretskii
2024-05-16 16:20           ` Duncan Greatwood
2024-05-16 18:18             ` Eli Zaretskii
2024-05-16 19:27               ` Duncan Greatwood
2024-05-16 19:51                 ` Eli Zaretskii
2024-05-16 21:36                   ` Duncan Greatwood
2024-06-01 14:04                     ` 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=86wmn8oj2q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=70973-done@debbugs.gnu.org \
    --cc=dgreatwood@gmail.com \
    /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.