That is not the story here. The story is Neovim deleted data created by another program, on someone else's computer.
replyI don't know if this story is true, but you can't defend it when taken at face value.
Do you have a link to how this happened? From what I understand you’d have to point the undodir at the same place as vim for this to happen? It’s not this way by default and you have to put a copy of the exact same thing in your neovim vimrc right without understanding that it would do this?
replyThat wasn't the point.
replyThe point was they did it in a completely stupid way and responded to a bug report about it in a way that suggested this might not be just the occasional stupid that we've all had slip into our code.
I think this might not be clear on the issue, it broke vim's undo file, as in it deleted it and replaced it with Neovims version.
replyJust by trying Neovim you can lose your vim undo file.
This is the crux of the matter. I wish a few of the "its OSS" commentators here would read this.
reply…and even trying Neovim out on a file permanently deletes your undo history for that file, even if you switch back to vim.
reply