From: Eli Zaretskii <eliz@gnu.org>
To: "Jay Berkenbilt" <ejb@ql.org>
Cc: 53207@debbugs.gnu.org
Subject: bug#53207: 28.0.91; create-lockfiles nil breaks file change detection
Date: Wed, 12 Jan 2022 19:26:22 +0200 [thread overview]
Message-ID: <83bl0g6f29.fsf@gnu.org> (raw)
In-Reply-To: <509ddd0f-589c-45b0-9b60-5820f4c1d716@www.fastmail.com> (ejb@ql.org)
> Date: Wed, 12 Jan 2022 09:30:07 -0500
> From: "Jay Berkenbilt" <ejb@ql.org>
>
> Bottom line: in emacs 27.2, setting create-lockfiles to nil does not change the behavior. In emacs 28.0.91, it does. I also noticed this in 28.0.90 but hadn't had time to figure out how to reproduce it without my customizations.
You seem to assume that create-lockfiles is _only_ about the creation
of the lockfiles. But that's not true: the variable is a misnomer,
and it actually controls the entire functionality of preventing
editing collisions. Including the test for the file being modified
behind Emacs's back. The doc string says:
Non-nil means use lockfiles to avoid editing collisions.
> Is this change intentional? If so, can I configure something to go
> back to the old behavior?
My suggestion is to stop setting create-lockfiles to a nil value. Why
is the non-nil value a problem?
next prev parent reply other threads:[~2022-01-12 17:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 14:30 bug#53207: 28.0.91; create-lockfiles nil breaks file change detection Jay Berkenbilt
2022-01-12 17:26 ` Eli Zaretskii [this message]
2022-01-12 20:07 ` Jay Berkenbilt
2022-01-12 20:45 ` Eli Zaretskii
2022-01-12 21:35 ` Jay Berkenbilt
2022-01-13 6:43 ` Eli Zaretskii
2022-01-13 13:06 ` Jay Berkenbilt
2022-01-12 18:13 ` Glenn Morris
2022-01-12 18:41 ` Philipp Stephani
2022-01-13 10:54 ` Eli Zaretskii
2022-01-13 13:11 ` Jay Berkenbilt
2022-01-13 13:24 ` Philipp Stephani
2022-01-13 14:02 ` Eli Zaretskii
2022-01-13 15:47 ` Jay Berkenbilt
2022-01-14 14:26 ` Michael Albinus
2022-01-14 14:43 ` Eli Zaretskii
2022-01-14 16:11 ` Glenn Morris
2022-01-14 16:44 ` Eli Zaretskii
2022-01-15 8:06 ` Lars Ingebrigtsen
2022-01-15 8:16 ` Lars Ingebrigtsen
2022-01-15 9:23 ` Eli Zaretskii
2022-01-27 17:19 ` Eli Zaretskii
2022-01-28 13:42 ` Lars Ingebrigtsen
2022-01-28 14:30 ` Eli Zaretskii
2022-01-28 14:56 ` Michael Albinus
2022-01-28 15:16 ` Eli Zaretskii
2022-01-29 10:53 ` Michael Albinus
2022-01-29 10:57 ` Eli Zaretskii
2022-02-03 13:31 ` Michael Albinus
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=83bl0g6f29.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53207@debbugs.gnu.org \
--cc=ejb@ql.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 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).