On Sat, 07 Mar 2009 at 08:11PM -0800, Byungchul Cha wrote:
> I experienced a similar problem and here's how I resolved it.
>
> First, I modified one line in my sagetex.sty file in my texmf
> directory (you said you put yours in ~/Library/texmf/tex/latex/) in
> order to specify the directory where sagetex.py can be found. The
> original sagetex.sty has a line
>
> %% \...@wsf{sys.path.insert(0, 'directory with sagetex.py')}
>
> and I changed this line to something like
>
> \...@wsf{sys.path.insert(0, '/Users/**yournamehere**/Library/TeXShop/
> Engines/Inactive/Sage')}That's good advice, although in the next release of SageTeX, it won't be necessary, since the sagetex.py file will automatically be included in Sage's Python library. > Secondly, your sagetex example file starts with > > %!TEX TS-program = sage > > This a TeXShop specific command. If everything is correctly set up, > TeXShop will do the latex-sage-latex process for you automatically. To > make it happen, you must move the sage.engine file from > > ~/Library/TeXShop/Engines/Inactive/Sage > > to > > ~/Library/TeXShop/Engines > > This will make the sage.engine file "active". > > With these changes, I compiled your example file in TeXShop. It runs > latex once and pauses (I suppose sage is fired up and is run at that > time) and then runs latex again. After that, a correct pdf output is > generated. I believe that this sage.engine is a new addition in the > most recent version (2.25) of TeXShop. Wow, that's cool! I'm really excited to see SageTeX included with TeXShop. I'll add this to the documentation. Dan -- --- Dan Drake <dr...@kaist.edu> ----- KAIST Department of Mathematical Sciences ------- http://mathsci.kaist.ac.kr/~drake
signature.asc
Description: Digital signature
