It's worth pointing out that vim is not "another program" as far as Neovim is concerned. It's an earlier version of the same program. Neovim is a fork of vim, not a totally different editor that happens to share part of a name.
replyForking creates new programs.
replyIf I fork chromium, I do not get to claim that I am a chromium maintainer.
Vim and Neovim are two seperate programs.
So maybe it should have two different undo files so both can be run side by side?
replyI am fairly certain that is the argument of the article.
replydeleted
replydeleted
replyIt absolutely is another program, I can tell this because it has a different name. To run it I type "nvim" instead of "vim". I use different config files to control its behavior. I install a different package on my system when I want to use it on a new computer.
replyIf it really is another program with reference to vim, it should leave undo files made by vim alone.
replyIf it's going to nuke vim's undo files, it can't hide behind "another program".
That is the point.
replyI don't understand. Are you saying neovim does not nuke vim's undo files? The whole point of the article is that it does.
replyIf that's not your point, then I have no idea what you're trying to say.
> I use different config files to control its behavior.
replyFrom what I can gather, you can use the same vimrc file to control both vim and neovim.