bug#23033: 24.5; Lock file uses the same extension as the file it's locking

[Stefan Kangas]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Is there any reason we don't just call these files .#foo.lock" or
> something?  Putting "lock" into the name would make it clearer to the
> users what these things are.

See below what Eli wrote earlier in this thread.

Eli Zaretskii <eliz@gnu.org> 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.

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.