On Mar 5, 10:32 pm, Jason Grout <jason-s...@creativetrax.com> wrote: > On 3/5/11 7:35 PM, kcrisman wrote: > > > > > > > > > On Mar 5, 6:22 pm, Thomas Rike<tricycle...@mac.com> wrote: > >> On Mar 4, 2011, at 3:03 PM, Benjamin Jones wrote: > > >>> You can try upgrading the Sage Jmol package manually. This has fixed > >>> some problems on Mac + Chrome systems. See this thread: > > >>>http://groups.google.com/group/sage-support/browse_thread/thread/4704... > > >>> -- > >>> Benjamin Jones > > >> The Sage Jmol package works fine in the terminal. It just won't work in > >> the notebook (Safari and Firefox give the same error.). I'm not sure how > >> to manually upgrade the Sage Jmol package, but I will try if I can get > >> specific directions. I no longer have a Sage directory since I am using > >> the Sage-4.6.1-OSX-64bit-10.6 app > > You definitely have a directory! It's just hidden. Crtl-Click on the > > app and you'll get a menu with "Show Package Contents" in it. Go to > > Contents/Resources and you'll find your sage directory. I feel like > > there is even a way to get that to open from the app, > > If you click on the "Development" menu, there is a Reveal in Finder > (which opens Finder to your Sage directory) or Reveal in Shell (which > opens your shell in the sage directory).
Good, so I was only spacey on one ticket tonight. I really need to just use the app; but it's so easy to click on the Terminal and type sage now that I finally made an alias for it. -- 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, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
