Your stated bug #1 is not a bug. The vi name is managed by the alternatives system. Packages with more functionality have a higher priority in the alternatives system. As such, installing the vim package installs a higher priority alternative for the vi name. If you want to use the vi binary from the vim-tiny package, then you can configure that by using the update-alternatives command.
The sole reason that vim-tiny's vi binary runs in compatible mode is because the binary is providing the expected vi that should be part of any base install of a unix system. This is the same reason that vim- tiny does not provide a binary that provides the vim name. By the sysadmin installing one of the other packages, they're no longer working with a base install and have expressed a desire to work with a more featureful Vim package. As far as your attempt at returning vi's behavior to that of vim-tiny, it is working under incorrect assumptions. Debian (and therefore Ubuntu's) packaging is what causes Vim to run in nocompatible mode by default. This is an intentional deviation from upstream which you eliminate by removing the system-wide configuration files. If you want vi to always follow vim-tiny's behavior, then you can change /etc/vim/vimrc to "set compatible" when v:progname is vi. Also, your attempt at recovering the behavior after removing the system- wide configuration files is flawed. By simply removing the packages (not purging them), you haven't done anything that affects the conffiles. A package's conffiles are only removed/forgotten by dpkg when you purge a package, not when you remove it. As such, reinstalling the removed packages has no effect on the conffiles you removed by hand. You, as the system administrator, took a specific action of removing the conffiles so dpkg is honoring your action. If you had purged the packages, then dpkg forgets its knowledge about the conffiles and a later reinstall will re-add the standard conffiles. -- vim (not vi) runs in compatible mode by default https://bugs.launchpad.net/bugs/667235 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
