>> It shouldn't overwrite an unreadable file tho, unless I have completely misread the code.
> It doesn't, but because it reads the vim-specific config file from the vim-specified location it then writes a file in that location with the name that vim expects, so files that I first edited in neovim ended up with undo files that vim couldn't read and vice versa. Both programs complained.
https://github.com/neovim/neovim/pull/13973#issuecomment-879...
>> It shouldn't overwrite an unreadable file tho, unless I have completely misread the code.
> It doesn't, but because it reads the vim-specific config file from the vim-specified location it then writes a file in that location with the name that vim expects, so files that I first edited in neovim ended up with undo files that vim couldn't read and vice versa. Both programs complained.