From: Michael Sloan <mgsloan@gmail.com>
To: 23033@debbugs.gnu.org
Subject: bug#23033: 24.5; Lock file uses the same extension as the file it's locking
Date: Wed, 16 Mar 2016 14:35:31 -0700 [thread overview]
Message-ID: <CAEDDsWf2QyABTDMAm_NDqtROiaagBVegq4JNxcKde2aXEYYG8w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
Lockfiles help the circumstance where multiple emacs processes are
editing the same file. The lockfile for 'File.hs' gets the name
'.#File.hs'. This means that naive enumeration of all the files in the
directory with the extension '.hs' will also yield the lockfile. Many
tools have behaviors that rely on enumerating all of the files which
have a particular extension, reasonably assuming that the user put them
there.
In particular, for me this caused the following issue:
https://github.com/commercialhaskell/stack/issues/1897
It seems wrong up for emacs to be writing files that have the extension
'.cabal' that are not cabal files. Even if they are named pipes that start
with '.', this causes problems for tools that expect files to be what their
name says they are.
Contrast this with backup files, which append a tilda to the end of the
filepath. This changes the extension, and so tools don't get confused
by the extra files.
Version info:
In GNU Emacs 24.5.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.12.2)
of 2015-09-10 on computer
Repository revision: 866501efe0fdc0c29448e0aaf8696eb0a3c8fcd6
-Michael
[-- Attachment #2: Type: text/html, Size: 1569 bytes --]
next reply other threads:[~2016-03-16 21:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 21:35 Michael Sloan [this message]
2016-03-19 2:09 ` bug#23033: 24.5; Lock file uses the same extension as the file it's locking Glenn Morris
2019-11-08 5:00 ` Stefan Kangas
2019-11-08 6:17 ` Michael Sloan
2019-11-08 13:29 ` Eli Zaretskii
2019-11-08 14:03 ` Stefan Kangas
2019-11-08 14:31 ` Eli Zaretskii
2019-11-08 13:24 ` Eli Zaretskii
2019-11-08 14:10 ` Stefan Kangas
2019-11-08 19:19 ` Eli Zaretskii
2019-11-09 6:17 ` Michael Sloan
2019-11-09 7:45 ` Eli Zaretskii
2019-11-09 9:12 ` Stefan Kangas
2019-11-09 9:24 ` Eli Zaretskii
2019-11-09 23:37 ` Michael Sloan
2019-11-14 9:17 ` Eli Zaretskii
2019-11-16 23:23 ` Michael Sloan
2021-09-25 0:06 ` Stefan Kangas
2021-09-25 1:49 ` Lars Ingebrigtsen
2021-09-25 2:10 ` Stefan Kangas
2021-09-25 2:27 ` Lars Ingebrigtsen
2021-09-25 2:59 ` Stefan Kangas
2021-09-25 3:05 ` Lars Ingebrigtsen
2021-09-25 3:45 ` Stefan Kangas
2021-09-26 5:28 ` Lars Ingebrigtsen
2021-09-26 6:31 ` Stefan Kangas
2021-09-26 6:34 ` Lars Ingebrigtsen
2021-09-26 7:17 ` Stefan Kangas
2021-09-26 8:24 ` Eli Zaretskii
2021-09-26 8:37 ` Andreas Schwab
2022-04-18 11:30 ` Lars Ingebrigtsen
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=CAEDDsWf2QyABTDMAm_NDqtROiaagBVegq4JNxcKde2aXEYYG8w@mail.gmail.com \
--to=mgsloan@gmail.com \
--cc=23033@debbugs.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).