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

[Stefan Kangas <stefan@marxist.se>]

Eli Zaretskii <eliz@gnu.org> writes:

> > I propose keeping the traditional `.#` prefix but adding a `.lock` suffix.

OK, if that works on Windows it's better than what I proposed.

> 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.

On this MacOS machine, I see the following:

$ ls -al
total 8
drwxr-xr-x  11 skangas  staff   352 Nov  9 10:05 .
lrwxr-xr-x   1 skangas  staff    33 Nov  9 10:05 .#foo ->
skangas@example.org.795
drwxr-xr-x  50 skangas  staff  1600 Nov  9 10:03 ..
-rw-r--r--   1 skangas  staff     0 Nov  9 10:03 a
-rw-r--r--   1 skangas  staff     0 Nov  9 10:03 e
-rw-r--r--   1 skangas  staff     3 Nov  9 10:05 foo
-rw-r--r--   1 skangas  staff     0 Nov  9 10:03 i
-rw-r--r--   1 skangas  staff     0 Nov  9 10:03 z

In other words, the lock file is not next to the file it locks.  Are
you seeing something else?

How would the ordering differ with a suffix like ".lock" compared to
"#" or some other punctuation character?  I would have thought that it
would be very similar.  Maybe I'm missing something.

Best regards,
Stefan Kangas