23 Mar
2013
23 Mar
'13
4:59 p.m.
On 03/24/13 05:43, Joe Zeff wrote:
On 03/23/2013 11:56 AM, Steven Stern wrote:
One of those things that can bite you in the butt is that the environment for /bin/sh might be different than than in /bin/bash, especially as invoked by cron.
Somebody suggested adding something new to crontab and seeing if it works. I tried it. Alas, even though I have both EDITOR and VISUAL set in both .bashrc and .bash_profile, crontab -e insists on invoking vi, an editor that I despise, and refuse to learn. (I prefer nano, and have that set as my default editor for EVERYTHING in a terminal.) Does anybody know how to force crontab to do what I want, not what it's author wants?
egreshko@meimei ~]$ export EDITOR=/usr/bin/nano [egreshko@meimei ~]$ crontab -e
--
>From now on, at least during winter time, Im going to blame all spelling an grammar erros on the cat sitting on my chest every time I sit down at the computer....