Re: backup-buffer-copy loops if old backup can't be deleted

[Richard Stallman]

    -                  (condition-case nil
    -                      (delete-file to-name)
    -                    (file-error nil))
    +                  (and (file-exists-p to-name)
    +                       (delete-file to-name))

I think that fix is actually correct.
It is copy-file that detects the race condition.
As long as copy-file is inside a loop, creation of
the file by another process will be dealt with.

So this change should be installed.

I think there is no need to explicitly check whether the directory
is writable.  What would be the purpose of that?