On Feb 22, 2011, at 14:52 , Jason Grout wrote: > On 2/22/11 3:10 PM, Justin C. Walker wrote: >> >> On Feb 22, 2011, at 11:44 , Jason Grout wrote: >> >> >> I don't see what you see; perhaps one of us has sufficiently strange setup >> in our startup files to either mask or cause the problems. > > It might be that I my default shell set to zsh. Could you try changing your > shell (using chsh) to zsh and then testing the value of $PATH after doing > sage -sh?
Gee. Ya think? :-} Here's what I get (again, fresh Terminal window): Last login: Tue Feb 22 15:10:38 on ttys009 zippo% echo $SHELL zsh zippo% PATH='.';export PATH /usr/libexec/path_helper -s zippo% /usr/libexec/path_helper -s PATH="/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/usr/texbin:/usr/X11/bin:."; export PATH; zippo% > It seems that when I set my default shell to bash, the $PATH variable is set > correctly in sage -sh. Doesn't the Sage environment kind of assumes 'bash' is your shell? I've never thought about it, but a quick check of '$SAGE_ROOT/local/bin' shows that at least some of the shell files insist on it. HTH Justin -- Justin C. Walker, Curmudgeon at Large Institute for the Absorption of Federal Funds ----------- Like the ski resort full of girls hunting for husbands and husbands hunting for girls, the situation is not as symmetrical as it might seem. - Alan MacKay -- -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
