From: "Jay Berkenbilt" <ejb@ql.org>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: 53207@debbugs.gnu.org
Subject: bug#53207: 28.0.91; create-lockfiles nil breaks file change detection
Date: Thu, 13 Jan 2022 08:06:24 -0500 [thread overview]
Message-ID: <f881c59b-87fc-4ad0-b1a1-5b76b239a946@www.fastmail.com> (raw)
In-Reply-To: <83mtk03zlp.fsf@gnu.org>
On Thu, Jan 13, 2022, at 1:43 AM, Eli Zaretskii wrote:
> > Date: Wed, 12 Jan 2022 16:35:15 -0500
> > From: "Jay Berkenbilt" <ejb@ql.org>
> > Cc: 53207@debbugs.gnu.org
> >
> > > > > My suggestion is to stop setting create-lockfiles to a nil value. Why
> > > > > is the non-nil value a problem?
> > > >
> > > > Emacs lockfiles are dangling symbolic links. Some tools and systems don't
> > > > like those.
> > >
> > > Isn't that the reason we introduced lock-file-name-transforms?
> >
> > Perhaps so, but this misses the point.
>
> My point was to say that if you want collision detection, you should
> turn on create-lockfiles. You said this could cause problems with
> some tools, and I then pointed out that Emacs 28 has a new feature to
> help you solve that side effect, so that you could use locking again.
Thank you for clarifying.
I have added the following to emacs initialization code. This is satisfying my
need to avoid dangling links in places that confuse tools.
=== 8< ===
;; I never use emacs with my own configuration in a multi-user
;; environment, and lockfiles are dangling links that confuse some
;; tools. Conflict detection works prior to 28.1 with
;; create-lockfiles nil. Starting in 28.1, it no longer works with
;; create-lockfiles nil, but lock-file-name-transforms can be used
;; to create the dangling links somewhere else. See
;; http://debbugs.gnu.org/cgi/bugreport.cgi?bug=53207
(if (boundp 'lock-file-name-transforms)
(let* ((lockdir (expand-file-name "~/.emacs.d/lockfiles"))
(replacement (concat lockdir "/\\2")))
(make-directory lockdir t)
(setq lock-file-name-transforms
`(("\\`\\([^/]*/\\)*\\([^/]*\\)\\'" ,replacement t))
)
)
(setq create-lockfiles nil)
)
=== 8< ===
> > It just seems strange that emacs is perfectly capable of detecting when a file was changed
> > outside of emacs without a lockfile but doesn't do this check if it's not also creating lockfiles.
>
> Once again, this is not about the lockfiles, this is about the entire
> feature of detection of editing collisions. The variable's name is a
> misnomer.
In addition to any other doc clarifications, I'd suggest the fact that create-lockfiles is a misnomer
be explained in the help for create-lockfiles.
I will add some thoughts to a different part of the thread. Thanks!
next prev parent reply other threads:[~2022-01-13 13:06 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
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 [this message]
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=f881c59b-87fc-4ad0-b1a1-5b76b239a946@www.fastmail.com \
--to=ejb@ql.org \
--cc=53207@debbugs.gnu.org \
--cc=eliz@gnu.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).