On 07/03/2015 05:23 PM, Carlos E. R. wrote:
On 2015-07-04 02:16, Carlos E. R. wrote:
On 2015-07-04 02:13, Patrick Shanahan wrote:
baffledthe environment
ps: ~/.bashrc *is* being read, but the editor not set ???
Try create a new user, and see there which is the default editor. If it is "vi", then it is something you changed on your user. If it is "mcedit", then it is some new default or behaviour...
Or a system wide setting, I forgot.
system wide settings (/etc/bash.bashrc) are overridden by personal settings (.bashrc) according to the manpage (crontab 1p) the environment variable EDITOR should control the editor, vi is the default. I would verify that EDITOR is correctly set (echo $EDITOR) I just a few experiments and found that EDITOR was set correctly (I set it to use joe) and crontab -e still used vi. I would tend to suspect that crontab itself is ignoring the variable, not that bash isn't reading .bashrc... And then I did this: export EDITOR=joe crontab -e and got joe as my editor! I'm wondering what happens if I log out and back in -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org