[IPython-User] PLEASE make autosave standard
Wed Nov 7 10:33:46 CST 2012
"In general, I don't think we'd block on a new feature. The standard for
setting a blocker is 'would we wait for this if everything else is ready
for a release?'"
Yes, I think bullet-proof crash data recovery is really that important for
some use cases.
"Could you flesh out a detailed description of how an autosave might work,
... It should describe, for instance:"
It doesn't matter to me as long as user input is on disk somewhere, in some
format. For example, the server could simply log the text of all the cells
that are sent for execution to a textual log file, even a single global log
file. Recovery would then be a few minutes of cut-and-paste, but that
beats starting from scratch.
(My preference is implementing Emacs autosave semantics; I tried explaining
how that works in an earlier message.)
"Looking at this differently, I wonder if we could use the localStorage
It's a workaround I can use myself, but I don't think it's a good solution
for the project.
On Wed, Nov 7, 2012 at 2:20 PM, Thomas Kluyver <email@example.com> wrote:
> On 7 November 2012 12:43, Tom <firstname.lastname@example.org> wrote:
>> (I think lack of autosave should be prio-blocker.)
> In general, I don't think we'd block on a new feature. The standard for
> setting a blocker is 'would we wait for this if everything else is ready
> for a release?' 0.14 will improve on 0.13 even if it's released without
> autosave, so it wouldn't make sense to hold it up for that.
> Could you flesh out a detailed description of how an autosave might work,
> perhaps as an IPEP (
> https://github.com/ipython/ipython/wiki/IPython-Enhancement-Proposals-%28IPEPs%29). It should describe, for instance:
> - What gets saved
> - Will it be always on, configurable, or 'smart'?
> - Where does it get saved? I don't like extra files cluttering up my
> working directory.
> - What happens if I have the same notebook open in two tabs? Or two
> computers talking to the same server?
> - Notebooks needn't be stored as files, they could be blobs in a database
> - how will this be abstracted away from the frontend?
> - Will autosave files be automatically removed, and if so, when?
> - How is a crash detected, and what UI presents the autosaves to the user?
> Looking at this differently, I wonder if we could use the localStorage
> share of difficulties, but perhaps it's worth exploring.
> IPython-User mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the IPython-User