From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
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:10:50 +0100 [thread overview]
Message-ID: <875zjutq51.fsf@marxist.se> (raw)
In-Reply-To: <83eeyicxh7.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 08 Nov 2019 15:24:20 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> 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.
My suggestion would be to add a one character suffix to the file name.
For example ".", so that:
lrwxrwxrwx 1 skangas skangas 30 2019-11-08 15:06 .#package.el -> skangas@joffe.31542:1572461517
Would instead look like:
lrwxrwxrwx 1 skangas skangas 30 2019-11-08 15:06 .#package.el. -> skangas@joffe.31542:1572461517
That, I think, looks visually not too busy.
(The most clear would be a suffix "-emacs-lock" or "-lock" but that is
probably too ugly and long.)
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2019-11-08 14:10 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
2019-11-08 14:10 ` Stefan Kangas [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875zjutq51.fsf@marxist.se \
--to=stefan@marxist.se \
--cc=23033@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mgsloan@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.