On 8/12/11 10:42 AM, samontab wrote:
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 scri
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
On Aug 7, 2011, at 5:26 AM, Jason Grout 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 o
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 out https://github.com/jasongrout/sage-forker which
allows for in
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 out https://github.com/jasongrout/sage-forker which
allows for instantaneous start up of an interactive
You can check what Sage-mode for emacs has done. Admittedly I never used it,
but it should resolve this problem exactly.
--
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
