all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: rgm@gnu.org, 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: Sat, 25 Sep 2021 04:27:25 +0200	[thread overview]
Message-ID: <871r5dpeya.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkmno-wPvfeReSzLBnCrdDKB3bhkvMvJZVEZjVvHrQ3R-cw@mail.gmail.com> (Stefan Kangas's message of "Fri, 24 Sep 2021 19:10:14 -0700")

Stefan Kangas <stefan@marxist.se> writes:

>> I think we should only consider adding punctuation characters, because
>> that would ensure these lock files are displayed right next to the
>> files they lock, like today.  Moving the lock files away of the files
>> they lock in the directory listing would be a disadvantage, IMO.
>
> I use LC_COLLATE=C, so I have never had these files next to each other,
> and never missed that feature either.

Yeah, they've never displayed close to each other for me, either.

> I also note that even with ".lock" the files are fairly close together,
> and they are also colored differently so they stand out.
>
> So from my perspective having the explanation ".lock" visible in the
> name is worth more than a slightly better sort order.

But would adding .lock to them change the sort order much?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-09-25  2:27 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
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 [this message]
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=871r5dpeya.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=23033@debbugs.gnu.org \
    --cc=mgsloan@gmail.com \
    --cc=rgm@gnu.org \
    --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 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.