leif wrote:
Alternatively, you could create scripts in $SAGE_LOCAL/bin/, which set
up what you need and then run Sage, but you'd have to start/run these
with './sage -c <my_script>'.

Ooops, './sage --sh <my_script>' of course.

(Since $SAGE_LOCAL/bin shouldn't be in your PATH, because the scripts there are supposed to get run in a Sage shell environment, i.e., with all Sage-relevant settings already made.)


-leif

--
() The ASCII Ribbon Campaign
/\   Help Cure HTML E-Mail

--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to