On May 29, 2014, at 4:50 AM, Dmitry Frank <[email protected]> wrote: > Could anyone explain why does Vim still have vi-compatibility mode? Why would > one use it? > > As a consequence, we have to keep set nocompatible in our .vimrc; there is > much noise in docs like {not in Vi}, {Vi: no ++opt}, etc. > > and I can't really understand why developers keep it so carefully. >
(Disclaimer: I'm not an official Vim developer and don't necessarily know the official reasons myself.) Tim Pope brought up the "vi equivalent" issue when Neovim was announced, I think back in February. "#1 concern about neovim is that dropping compatibility mode prevents OS's from shipping it as vi. That's a big perk of vim" https://twitter.com/tpope/status/437019518444240896 That could have something to do with it. On the other hand, I am on OS X, which is one of those OSs. I installed Vim using Homebrew anyway -- and I don't actually often use many other computers than my own (though I realize that many must). So the "Vim is everywhere" argument, for me, has very little to do with why I use it, and is no argument (for me personally!) in favor of compatibility mode. The mileage of the sane rest of the universe probably varies. Ben -- b Sent from my iPhone -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
