From: Lars Ingebrigtsen <larsi@gnus.org>
To: Nicolas Calderon <nicolas.calderon.asselin@gmail.com>
Cc: 20659@debbugs.gnu.org
Subject: bug#20659: auto-save-visited-file-name: leaks interlock files and abandons unsaved buffers
Date: Sat, 23 Jan 2021 22:45:10 +0100 [thread overview]
Message-ID: <87a6sztjix.fsf@gnus.org> (raw)
In-Reply-To: <CAHbMD+H5BLF5Z5w-N6sYOdQBrTHuErNnprsacH44T3eWZPwhiw@mail.gmail.com> (Nicolas Calderon's message of "Tue, 26 May 2015 01:38:54 -0400")
Nicolas Calderon <nicolas.calderon.asselin@gmail.com> writes:
> When auto-save-visited-file-name is set, emacs auto-saves directly to
> file rather than a different file (#<filename>#). Unfortunately,
> auto-saving does not get rid of the interlock file (symlink from
> .#<filename> -> <user>@<host>.<pid>:<uid>). Since the buffer is saved
> and not modified (buffer-modified-p is false, as evidenced by the
> modline), emacs can be exited without the "Save file?" prompt. Leaving
> emacs at this point, without making a proper save (save-buffer),
> leaves the interlock files behind modifications directly to the file
> rather than auto-saving.
(I'm going through old bug reports that unfortunately got no response at
the time.)
I'm not able to reproduce this bug in Emacs 28, and indeed this has all
been rewritten in 2017:
commit 4db844a4532592ed2542c05a1747dad7ed319e15
Author: Philipp Stephani <phst@google.com>
AuthorDate: Sat Apr 22 20:58:38 2017 +0200
Reimplement auto-saving to visited files
This reacts to confusing behavior of 'auto-save-visited-file-name',
cf. Bug#25478.
So I'm going to go ahead and guess that this has been fixed by now, and
I'm closing this bug report. If there are still bugs in this area,
please respond to the debbugs address and we'll reopen.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-01-23 21:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 5:38 bug#20659: auto-save-visited-file-name: leaks interlock files and abandons unsaved buffers Nicolas Calderon
2021-01-23 21:45 ` Lars Ingebrigtsen [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a6sztjix.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=20659@debbugs.gnu.org \
--cc=nicolas.calderon.asselin@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).