On 07/03/2015 06:37 PM, Patrick Shanahan wrote:
* Bruce Ferrell
[07-03-15 21:35]: On 07/03/2015 06:26 PM, Patrick Shanahan wrote:
* Bruce Ferrell
[07-03-15 21:15]: [...] And the winner is...
When the syntax in .bashrc is:
EDITOR=/usr/bin/joe
EDITOR is "set" and not available i.e. echo $EDITOR show /usr/bin/joe but it doesn't work
EDITOR=/usr/bin/joe export EDITOR
or
export EDITOR=/usr/bin/joe
results in the variable set and usable
crontab -e
get's joe as it's editor
the moral of the story is bash variables must set AND exported Forget crontab.
In ~.bashrc I have: export EDITOR=/usr/bin/joe
I start a new shell echo $EDITOR /usr/bin/mcedit
THAT is not right!
I can change ~.bashrc to EDITOR=/usr/bin/joe export EDITOR
with the same result, /usr/bin/mcedit! after changing .bashrc, do you reload it?
. .bashrc
If you're in the same terminal session that you edited .bashrc, it hasn't been re-read and the variable isn't effective in the current context Yes, and/or start another shell or another bash instance
bash edit .bashrc bash echo $EDITOR /usr/bin/mcedit
You are correct, a new shell will re-read .bashrc. There is something quite odd about your system -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org