On Jan 23, 2012, at 7:23 PM, Jeroen Demeyer wrote: > On 2012-01-22 17:28, Ivan Andrus wrote: >> On Jan 22, 2012, at 1:11 AM, Volker Braun wrote: >> >>> sage-native-execute should remove all traces of Sage in from the >>> environment, but there is definitely stuff falling through the cracks. But >>> I don't understand why one would want to start sage via >>> sage-native-execute, unless one wants to run a potentially different sage >>> version that is globally installed? >> >> I have to start the notebook in an interactive way so that the user can type >> in a password the first time they run the notebook. I'm sure there are a >> number of ways to work around it, but the easiest way is to run Sage in >> Terminal.app so they can interact with it. So I run Terminal.app and tell >> it to run sage. That's why it showed up in this case. > > Why do you need sage-native-execute then?
Because using osascript to open Terminal.app segfaults otherwise. Also, the PATH can get messed up in the process because Terminal.app runs sage in a shell thereby executing .bashrc etc. Or perhaps your question was why am I running it after sage-env has been sourced? Well that could probably be changed but I was running it after I checked to make sure the location hasn't changed. -Ivan -- 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
