Le mercredi 22 mai 2019 10:00:34 UTC+2, John Cremona a écrit : > > Paul Zimmermann suggested using -nodotsage, which apparently creates a > temporary .sage directory which I expect would be different for different > runs. This is not ideal since currently the scripts I am running this way > make use of a %runfile command in ~/.sage/initsage to load all the > functions needed. >
One can use a custom init.sage, see my answer to - Stack Overflow question 41922740: Start cli with init.sage https://stackoverflow.com/questions/41922740 The trick is just to use the SAGE_STARTUP_FILE environment variable. Instead of just running $ sage run $ SAGE_STARTUP_FILE=/path/to/custom/init.sage sage -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/47d12b47-1a03-4fd3-adbd-52ae32b93470%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
