[Bug 372588] Re: sudo crontab -e uses wrong vi version

2018-04-11 Thread Lucas Sandery
In this case, when update-alternatives does not work, try select-editor instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/372588 Title: sudo crontab -e uses wrong vi version To manage notific

[Bug 372588] Re: sudo crontab -e uses wrong vi version

2010-05-13 Thread Will Gray
This really has nothing to do with Vim and all to do with environments and Sudo. ** Changed in: vim (Ubuntu) Status: New => Invalid -- sudo crontab -e uses wrong vi version https://bugs.launchpad.net/bugs/372588 You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 372588] Re: sudo crontab -e uses wrong vi version

2010-03-13 Thread fiery
It appears sudo doesn't source root's preferences. To fix: First, make sure that vim is set as root's EDITOR by placing this in /root/.bashrc export EDITOR=/usr/bin/vim Now, use the -E switch to tell sudo to use root's environment variables, i.e. to source /root/.bashrc. So your command sho

[Bug 372588] Re: sudo crontab -e uses wrong vi version

2010-03-03 Thread Daniel Nelson
I have this problem after installing vim with aptitude install vim nd using update-alternatives --config editor to select vim. Only crontab -e doesn't work, visudo opens vim as expected. -- sudo crontab -e uses wrong vi version https://bugs.launchpad.net/bugs/372588 You received this bug notifi

[Bug 372588] Re: sudo crontab -e uses wrong vi version

2009-08-05 Thread primefalcon
of course make sure you have vim installed properly by sudo apt-get install vim, on OS install it only typically installed a mini version of vim. probaly because not everyone uses vim -- sudo crontab -e uses wrong vi version https://bugs.launchpad.net/bugs/372588 You received this bug notificati

[Bug 372588] Re: sudo crontab -e uses wrong vi version

2009-08-05 Thread primefalcon
Add EDITOR=vim to the bottom of your .bashrc file, which is located in your home directory. That should fix the issue after you reboot To save you rebooting, the following command in the terminal will make this functional as of now export EDITOR=vim -- sudo crontab -e uses wrong vi version h