> It is not the case that the current lock file names are always listed next to the files they are clocking:
>
> mgsloan@treetop:~/test$ ls -la
> total 8
> drwxrwxr-x 2 mgsloan mgsloan 4096 Nov 9 16:36 .
> drwxr-xr-x 57 mgsloan mgsloan 4096 Nov 9 16:35 ..
> -rw-rw-r-- 1 mgsloan mgsloan 0 Nov 9 16:36 .#test.md
> -rw-rw-r-- 1 mgsloan mgsloan 0 Nov 9 16:36 '#.test.md'
> -rw-rw-r-- 1 mgsloan mgsloan 0 Nov 9 16:35 test.md
I agree that it is easy to cook an example where this doesn't happen,
but usually it does.
Indeed! And appending ".lock" to a file name is also typically adjacent in listings, and it is easy to cook an example where it is not.