> > > No, it's not infeasible. We'd just have to maintain two copies of the > > > worksheet, and only have the permanent one overwritten during the > > > autosave interval or when you explicitly press Save. > > > > It sounds like if we got the snapshots working, that might give you what > > > you want. Under that system, every time you press "Save", it saves a > > > snapshot, which you can revert to if you'd like. Unfortunately, > > > snapshots have been broken for a long time now. Volunteers to fix them > > > are more than welcome! > > > The real question is how they got broken in the first place? > > We purposely turned them off because they wasted too much disk space. We > need to implement them better, e.g., using a revision control system like > hg or git.
That's not what I asked. I know the story behind how the autosave got more or less turned off. My question is why save is BROKEN, namely why every time you save, ALL the previous revisions (which are still available in the history tab or whatever it's called now) become the same as the current revision. That doesn't waste too much disk space, or else we would have turned even regular saving off completely. Again, did all Google Code issues migrate to github? http://code.google.com/p/sagenb/issues/detail?id=58 http://code.google.com/p/sagenb/issues/detail?id=59 - kcrisman -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
