Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#25815 - crontab -e uses vi by default and vi isn't a dependence.
Attached to Project:
Arch Linux
Opened by Leandro Costa (lokidarkeden) - Monday, 29 August 2011, 19:45 GMT
Last edited by Jan de Groot (JGC) - Monday, 29 August 2011, 20:59 GMT
Opened by Leandro Costa (lokidarkeden) - Monday, 29 August 2011, 19:45 GMT
Last edited by Jan de Groot (JGC) - Monday, 29 August 2011, 20:59 GMT
|
DetailsDescription:
Hi, when we do: crontab -e, it try to use vi to open the configuration file. It blames me for don't have the vi installed :) /usr/bin/vi: No such file or directory Issue fixed by install vi: pacman -Sy vi. Thanks for your attention Additional info: * package version(s) dcron 4.5-2 vi 1:050325-1 * config and/or log files etc. Steps to reproduce: |
This task depends upon
Closed by Jan de Groot (JGC)
Monday, 29 August 2011, 20:59 GMT
Reason for closing: Not a bug
Additional comments about closing: See first response. Also note the EDITOR variable, crontab -e can use whatever you want, even gedit.
Monday, 29 August 2011, 20:59 GMT
Reason for closing: Not a bug
Additional comments about closing: See first response. Also note the EDITOR variable, crontab -e can use whatever you want, even gedit.
You can use nano too:
[karol@black ~]$ export EDITOR=nano
[karol@black ~]$ crontab -e
/bin/sh: nano: command not found