@daniel.e2718, it is actually easy to implement. Sage 5.0 comes with sagetex installed. You can verify this by typing at the sage command prompt sage -i | more to view a list of installed packages. You will see sagetex-2.3.3.p2. This means all you have to do is share the windows folder that is your tex working directory. You do this by going to Oracle VM VirtualBox Manager, selecting the Machine->Settings menu path and finally selecting Shared Folders on the left navigation pad. Finally, as The SageTEX package pdf manual states,
To copy the fi les that LATEX needs into your texmf directory (your windows shared folder), simply do
cp -r $SAGE ROOT/local/share/texmf/* HOMEPREFIX/texmf/
You can test your windows tex editor with the provided example.tex now located under your shared folder:
Okay. What do you mean by "tex working directory"? I'm not familiar with command lines at all, so I don't know if `cp -r $SAGE ROOT/local/share/texmf/* HOMEPREFIX/texmf/` needs adjustment -- i.e., do I need to change a directory? And when you say build the *.tex file, do you mean run PDFLaTeX on it or just write it up?
See http://www.sagemath.org/doc/installation/sagetex.html for more information. The `$SAGE_ROOT` band so forth will indeed need adjustment, based on where you have installed Sage and where your Windows directory is (I am not quite sure what `HOMEPREFIX` is but I bet you can look it up). "Build the file" means to actually run (pdf)LaTeX on it, you are correct.
That link says `$SAGE_ROOT` is the location of my Sage installation. I have no idea how to find that out.
Assuming you are at some point in the command line, where do you go to run Sage? Wherever that is, type `pwd` and it should probably end with `.../sage-x.y.z/` or something, and that would be the Sage root. Without knowing exactly how you're trying to do this, it's difficult to help; maybe opening a different question would be more helpful.
Asked: 2012-05-30 13:28:58 +0100
Seen: 1,180 times
Last updated: Jun 14 '12
Copyright Sage, 2010. Some rights reserved under creative commons license. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
I second this, but I have no idea how difficult it would be to implement it.