My personal opinion is that if you are using `vi` you expect vim to behave like `vi` (set cp); and that if you use `vim`, you expect the command to behave like vim (set nocp).
That being said, I would admit `vi` is pretty much lost in history. To that, I'd even propose the pedantic route of removing the `vi` alias if the command isn't `vi` anymore, but that might be going too far. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/2107647 Title: Drop compatible mode for vim-tiny Status in vim package in Ubuntu: Triaged Bug description: I know I'm opening a can of worms here, but maybe we could drop `set compatible` from /etc/vim/vimrc.tiny. I think who needs the compatible mode these days knows where it can find it and how to enable it, and it's really annoying in a fresh installation to get the strange characters when using the arrow keys. Possibly 10–15 years ago, it would make sense to have vim-tiny using compatible mode, but today we could, and even should, rethink about it. I know `nano` is the default text editor, but we discuss `vi` a lot in technical documentations, so my opinion is we should provide a nice experience for the user. I understand `vi` in general isn't a nice experience for a beginner user, though, but not using compatible mode would be s little less daunting. But I'm thinking if there is any tool that would need to invoke `vi` in compatible mode, that could cause a problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2107647/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
