Your description sounds like you are doing a hg_sagenb.commit(), not a
hg_sagenb.apply("http:/..../<patchname>.patch"). If you just copy
the link to the listed patches as shown above they should work.
That's what I do.
Jonathan
P.S. Great name!
On Mar 31, 11:32 am, jtyard <jty...@gmail.com> wrote:
> Hi Jonathan,
>
> Thanks for your reply. I tried last night to figure out how to patch
> my notebook, and I ended up giving up after several hours. I also
> couldn't find any documentation for hg_sagenb.apply. After updating
> jmol to 1.1.5, I tried to follow the directions at
>
> http://www.sagemath.org/doc/developer/walk_through.html#reviewing-a-p...
>
> only replacing hg_sage.apply with hg_sagenb.apply, but things seem not
> to be as simple as described on that page. Running the command on a
> patch drops me into a vim editor that shows the text of the whole
> patch. Not knowing what to do, I press "q" and I am then asked to
> enter a commit message. No matter what I seem to do, when I try to
> quit vim it warns me that there was "no write since last change", and
> if I quit with :q! then it seems I am back where I started. It
> doesn't help that I am next to clueless about vim, having been raised
> on emacs, but I really am beyond confused about why I am being dropped
> into the editor in the first place.
>
> Any pointers you could give me to get the new notebook up and running
> would be much appreciated. I'll be more than happy to test it.
>
> Thanks,
> Jon
>
> On Mar 31, 7:08 am, Jonathan <gu...@uwosh.edu> wrote:
>
> > Jon,
>
> > We are sorting this out. Ticket #9238 is the one you want.
> > The .spkg you used is out-of-date. All the fixes are not in, but if
> > you follow the patching instructions on #9238 you should get something
> > that will work cleanly on MacOS + Chrome. FF has been inconsistent,
> > so we are having trouble tracing the error and Safari appears to have
> > a memory leak (the latest patches have a clunky work-around for this).
>
> > If you want to see what is coming down the pike in the next few
> > weeks, take a look at the published samples on my test server:
> > http:///141.233.197.45:8888. I could really use some comments on how
> > it works.
>
> > Thanks,
> > Jonathan
>
> > On Mar 30, 12:02 am, jtyard <jty...@gmail.com> wrote:
>
> > > I am having issues with sage notebooks that contain more than five
> > > instances of the Jmol viewer. In short, if I create a notebook with
> > > more than 5 Jmol viewers, save, then reload it, I get an unresponsive
> > > script error in Firefox, Safari and Chrome. I've done some peeking
> > > around on the trac server and it seems that this is a well-documented
> > > problem for which a fix may exist, having to do with the tickets #9232
> > > and #9238. So I apologize if this is not the correct place to ask
> > > about this, but I'm having trouble following what has been done on
> > > these tickets and, more importantly, what I would need to do in order
> > > to incorporate the fix to my sage distribution. I'm running sage
> > > 4.6.2 on osx 10.6.7, and I upgraded to
> > > Jmol_for_SageNoteBook-1.1.4.spkg so that I could use google Chrome.
>
> > > I'm sure that if I wait long enough this will all be incorporated into
> > > an upcoming release of sage, but I'd be very happy to resolve this
> > > issue asap so that I can use my notebooks without deleting all the 3d
> > > plots. I'm also more than happy to test the changes, but any pointer
> > > to how I can incorporate the new code would be helpful.
>
> > > Thanks,
> > > Jon
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
