From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 23033@debbugs.gnu.org, mgsloan@gmail.com
Subject: bug#23033: 24.5; Lock file uses the same extension as the file it's locking
Date: Fri, 08 Nov 2019 15:24:20 +0200 [thread overview]
Message-ID: <83eeyicxh7.fsf@gnu.org> (raw)
In-Reply-To: <87pni3t129.fsf@marxist.se> (message from Stefan Kangas on Fri, 08 Nov 2019 06:00:14 +0100)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Fri, 08 Nov 2019 06:00:14 +0100
> Cc: 23033@debbugs.gnu.org, Michael Sloan <mgsloan@gmail.com>
>
> As much as I agree with the general sentiment above, one could also
> consider users who are running e.g. 'find -iname "*.hs"' and are not
> necessarily interested in seeing Emacs lock files. IOW, if this is
> not a big change, it could be worth doing it.
What change did you have in mind? AFAICT, no specific change was
proposed in that bug report.
The advantage of the current method is that Dired and 'ls' display the
lock file right near the file that is locked, at least on most systems
and with the default file sorting order. If the change proposal will
order them far apart, it would be a disadvantage.
next prev parent reply other threads:[~2019-11-08 13:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 21:35 bug#23033: 24.5; Lock file uses the same extension as the file it's locking Michael Sloan
2016-03-19 2:09 ` 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 [this message]
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=83eeyicxh7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23033@debbugs.gnu.org \
--cc=mgsloan@gmail.com \
--cc=stefan@marxist.se \
/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).