bug#43535: File locking on Windows

[Lars Ingebrigtsen]

Richard Copley <rcopley@gmail.com> writes:

> Parse failure in "current_lock_owner" isn't handled well. You can
> force the same issues to occur on a non-Windows system by deleting the
> ".#x" symlink and recreating it with a bad target.

I tried reproducing this in Debian:

cd tmp
touch foo
ln -s noexist .#foo

and then editing and saving /tmp/foo:

Warning (unlock-file): Unlocking file: Invalid argument, /tmp/foo, ignored

So a warning pops up here...  which I think is reasonable?

Do you see something different?

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