#18951: Instructions for using SageTeX with TeXShop
---------------------------------+--------------------------
       Reporter:  kcrisman       |        Owner:
           Type:  defect         |       Status:  needs_info
       Priority:  critical       |    Milestone:  sage-6.8
      Component:  documentation  |   Resolution:
       Keywords:  SageTeX        |    Merged in:
        Authors:                 |    Reviewers:
Report Upstream:  N/A            |  Work issues:
         Branch:                 |       Commit:
   Dependencies:                 |     Stopgaps:
---------------------------------+--------------------------
Changes (by ddrake):

 * status:  new => needs_info


Comment:

 I checked on a Mac running 10.9 with a recent version of TeXShop (3.2ish,
 3.3ish, I think) and can't reproduce the problem. In fact, I can't imagine
 this really is a problem with TeXShop; TeX has its own path-searching
 mechanism and it would be really bizarre if TeXShop somehow altered that.
 If `sagetex.sty` is findable by TeX (via something like `kpsewhich
 sagetex.sty` in a terminal) then I would be very surprised if there's a
 problem when typesetting from TeXShop. I would need more information (and
 a Mac, since I don't have one these days) to figure out those problems.

 Also, I see that
 [[http://pages.uoregon.edu/koch/texshop/changes_3.html|TeXShop's changelog
 for 3.22]] has exactly the correct solution to making the `.sty` file
 findable, even on upgrades;
 [[http://faculty.essex.edu/~bannon/sp/sagetextexshop.pdf|Ron Bannon's
 notes]] also have good advice. So I don't see anything to do as far as
 making the `.sty` file available; our own instructions, and those from the
 TeXShop folks, are all correct as far as I can see.

 As for moving the `.engine` file: this isn't something we have control
 over. TeXShop ships with Sage's engine in the Inactive folder and you have
 to move the file. Once you've moved it, it should stay there; if it gets
 overwritten, then that's a TeXShop problem.

 As for what you do when you upgrade Sage: it's the same as when you
 install it, unless you symlink `sagetex.sty`, in which case you do
 nothing. SageTeX has version mismatch detection, so if someone upgrades
 Sage (with a new version of SageTeX), they should see an error and be able
 to fix it by moving the `.sty` file appropriately.

 I'm seeing a bunch of vague issues which are either not actually problems
 that we can solve, or for which we don't actionable information. I'm
 marking this as "needs info", but I recommend we close it. The only thing
 I see here that we can do is add something to the
 [[http://doc.sagemath.org/html/en/tutorial/sagetex.html#sec-sagetex-
 install|installation guide]] about upgrading...but it already says you
 should recopy the directory. Do you want to mention symlinks?

--
Ticket URL: <http://trac.sagemath.org/ticket/18951#comment:4>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" 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-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to