Thanks for the suggestions. sage forker works fine on my machine. The startup of sage is almost instant now. I have a problem though. Normally I would call sage scripts like this:
sage script.sage I tried using fsage for executing the scripts: ./fsage script.sage But it only starts sage (very fast though), without executing the script. Is it possible to do such thing?. If that cannot be done, I guess my only choice will be to use the simple web server.... but it does not support the console commands like "ls", "pwd", etc. (or at least I can't get them to work). On Aug 6, 11:26 pm, Jason Grout <jason-s...@creativetrax.com> wrote: > On 8/6/11 4:09 PM, Ivan Andrus wrote: > > > On Aug 6, 2011, at 6:19 PM, Rado wrote: > > >> You can check what Sage-mode for emacs has done. Admittedly I never used > >> it, but it should resolve this problem exactly. > > > You may also want to check > > outhttps://github.com/jasongrout/sage-forkerwhich allows for instantaneous > > start up of an interactive shell. > > I have an updated version of that which I have not posted yet. Sometime > next week... It solves some problems like: > > 1. forking erases history > > 2. forking always starts in the same directory as the original server, > not in the current working directory > > 3. the pipe was not specific to a computer (important when you're on NFS > and trying to run a forking server for multiple computers with a shared > home directory) > > and a few other things... > > Jason -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
