> > > I keep getting notebooks that are messed up: text and formulas have been > > randomly moved around and some are missing. I think this happens when > > closing the Sage notebook without either saving or discarding the changes. > > I haven't changed any of the default settings. Unfortunately, quitting out > > of Sage without properly saving happens fairly frequently, and it is
Really? Even if you accidentally go forward or back in your browser history, usually returning brings you back to the correct state, in my experience (and I've dealt with this bug a lot over the years). The save and save and quit buttons work well, as far as I can tell. > > extremely annoying to lose not just the unsaved changes, but to end up with > > a completely messed up notebook that may take as long to put in order again > > as it took to write originally. > > > Is there any way I can avoid these problems? Is there any solution on the > > horizon? The current situation really makes Sage feel very flaky and > > unreliable, and it makes me reluctant to rely on it or the integrity of > > results that come out of it, since I can never tell whether a notebook > > really is up to date and correct. Forwarding this to sage-devel and sage-notebook. Primarily because of the very accurate, if caustic, adjectives used by the post - this *needs* to be taken care of. Whatever happened when the auto-save was disabled is not sufficient. This has been known for a long time, and unfortunately we simply cannot figure out how to fix it - yet - because we have never seen a report that indicates how to reliably reproduce it. Many of us have tried! However, anecdotal evidence is that the flask-based notebook may have solved this. This still needs further testing before it becomes part of Sage proper, but would be welcome news. > > At the very least, there should be a warning when users try to close a page > > containing an unsaved notebook, and there should be another warning if a > > notebook that wasn't properly closed is opened again. Thoughts? > > I sincerely support your urgent request. In the past I have indicated > this annoying Sage habit more than once. > There is a log facility, but to repair a scrambled notebook file is > much work, and often not worth the effort. > > I suggest for instance an user set option which ensures 15 minutes > safe of a *.txt file (not *.sws!). Again, this used to be the case, and I believe still is an option, though perhaps very poorly documented. > Or maybe %safe per cell and %autosafe for the whole notebook are a way > forward. With these options, I'm (as user) fully aware what is > essential to save extra (to avoid new memory problems et cetera). The > save location should be as safe as possible, of course. > Maybe version 4.7.1 will be improved .... I keep my fingers crossed. > Roland -- 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
