On Wed, Dec 9, 2015 at 1:35 AM, Paul Leopardi <paul.leopa...@gmail.com> wrote: > I also could not reproduce the problem with the worksheet you gave me. I > have reproduced it with the following worksheet > https://cloud.sagemath.com/projects/80f4c9e7-8a37-4f59-82e7-aa179ec0b652/files/public/new-order.sagews > which leads me to believe that it is caused by a 'corrupted' worksheet. My > guess is that the corruption occurs either when I change the contents of a > cell while a calculation is running in that cell or another cell, or I > change the contents of a cell after an unsuccessful attempt to stop a > calculation, possibly followed by a restart. I have done this many times > over the course of creating my larger worksheets, but have not yet nailed > down the problem.
Thanks. I will be rewriting Sage worksheets in the near future (probably Jan) to take into account planned improvements to sync and our switch to react.js, and plan to come up with a much more robust editing model. William -- William (http://wstein.org) -- 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 sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
