If a system-wide or personal bashrc startup file sets the $PATH, it seems to overwrite any customizations in sage -sh. In looking into this, I see that at the top of sage-sage, we have:
. $SAGE_ROOT/local/bin/sage-env 1>/dev/null 2>/dev/null and then later on, the shell is just executed, possibly with some options to avoid all initialization. So it seems that the choices are *no* initialization, or a default initialization that could possibly wipe out the sage-env customizations. (For you shell experts) What is the best way to have a newly-started shell to execute a file (sage-env) after starting up? Maybe the -c command to evaluate the sage-env script again in order to prepend the things on $PATH, etc.? Thanks, Jason --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
