OK so my command line in TeXMaker is "/usr/local/bin/sage" %.sagetex.sage
I have made a simlink (sudo ln -s ...) from the sage exec in the Sage app folder : /Applications/Sage-6.1.1.app/Contents/Resources/sage/ and I placed it in my /usr/local/bin folder. The previous simlink was actually pointing to the wrong exec. It could launch the Sage frontend just fine but I could not throw stuff at it. The wrong location is /Applications/Sage-6.1.1.app/Contents/MacOS/ under the name Sage (with upper-case S). So I run pdfLaTeX on the file and then I do alt+shift+F1 and it runs the Sage script from within TeXMaker. The files are now created in the right folder (containing example.tex) and everything works fine, except for the tkz-berge part but standard tikz code works just fine. I hope this helps. Samuel Le mercredi 19 mars 2014 17:12:07 UTC+1, Dan Drake a écrit : > > On Tue, 18 Mar 2014 at 01:52PM -0700, [email protected] <javascript:>wrote: > > It worked! So now I know what to do: point to the right sage exec in the > > sage app folder lol! There are 2 and my simlink was pointing to the > wrong > > one. > > I'm glad to hear you have it working! > > I'd like to include some documentation of this. What exactly did you use > for the user command to run Sage? > > Thanks, > > > Dan > > -- > --- Dan Drake > ----- www.math.wisc.edu/~ddrake/ > ------- > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
