Related:
Bug #70569 – Vim variants other than vim-tiny source /etc/vim/vimrc
instead of /etc/vim/vimrc.tiny when invoked as vi (ie, Arrow keys
not broken when running vi)
https://bugs.launchpad.net/ubuntu/+bug/70569
It seems to be a long-standing issue: that bug was filed in 2006. The
discussion there is an interesting read. It seems to me that there is no
general agreement on what the right behavior should be.
I am not marking this as a duplicate, as that bug makes almost the exact
opposite complaint. Namely that *only* vim.tiny starts in compatible
mode when invoked as ‘vi’.
> it can be frustrating for a non-so-experienced user, considering they
> are using vi instead of nano
Vi, just like emacs, should never be used by someone who is unaware of
its learning curve. Even if you fix the arrows-in-insert-mode issue,
there is no way an unaware user can even exit the editor!
Don't laugh. This happened to me, as a new vi user, in 1993. I started
vi and got stuck in it, as I could not find my way out. See the outcome:
thirty-two years later I am still using vi (although it's now vim).
> I ran a fresh container with multipass and the problem didn't happen
> because it uses vim.basic instead.
I also found vim-basic providing ‘vi’ on a VM freshly installed from the
server ISO.
> Maybe do the desktop image using vim.basic too?
Not sure. On both my Ubuntu desktops, vi is provided by vim-gtk3, but
that is not part of the default installation. I can't tell what vi
provider comes in a fresh install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2107647
Title:
Drop compatible mode for vim-tiny
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2107647/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
