Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Install vim-enhanced 2.Log in and type 'alias' Note that 'vi' is aliased to 'vim' correctly. 3.su - 4.as root user edit some .spec file Actual results: vi was not aliased to vim and text isn't color coded Expected results: vi should be aliased to vim and text is color coded Additional info:
Created attachment 118680 [details] my propose patch
using /bin/vi for users with UID < 100 including UID 0 is intentional and was made by the request of many users. /usr/bin/vim won't work for sysadmins on many cases, p.e. if /usr isn't mounted or is mounted via NFS and the NFS server is down. /bin/vi will still work in those cases.
Sorry can't agree it that, because those are 1% of cases and those users should use /bin/vi like you write. The others 99% are losing the benefits of vim.
Well, lets try another reasoning: when root types 'vi', he will get a editor as it is defined in the POSIX standard. 'vim' on the other hand isn'T POSIX compatible.