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

[Lars Ingebrigtsen]

Stefan Kangas <stefan@marxist.se> writes:

> I don't even understand why you would need to see that file.  It almost
> seems better to not see it at all, or keeping it outside of the
> directory, given that we have many other things in place to help the
> user notice and deal with file locking and conflicts.

I've started using lock-file-name-transforms myself to put the lock
files somewhere else, but most people will use the defaults here, and if
we want to change anything here, I think we have to tread carefully.
That is, if we introduce a change that makes things sort differently, we
should have a really good reason to do that, because it will annoy
(some) users.

So perhaps adding a "#" (or some other non-alphabetic character) at the
end is the solution that will have the least friction?  Are there any
other characters we could be using?  %?

> I just checked some other editors:
>
> - vim uses ".foo.swp"
> - nano uses ".foo.swp"
> - VSCode has no swap file (or it's not in the directory)
> - GEdit has no swap file (or it's not in the directory)

And these swap files serve the same purpose as our lock files?

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