Saving Without Checkpointing
236 views
Skip to first unread message
Lawrence D’Oliveiro
Jun 30, 2016, 11:55:23 PM6/30/16
to Project Jupyter
One curious lack from the notebook interface is a function for saving the current notebook without creating a checkpoint as well. Personally I haven’t used the checkpointing function much. Maybe others will point out how useful it has been to them. :)
Anyway, besides waiting for the periodic autosave, I found a way to manually trigger a save at any time: simply try to close the browser tab/window for that notebook. If you have unsaved changes, you will get a confirmation dialog asking you if you really want to leave, or stay. And it turns out, whichever one you choose, it will still save the notebook!
Anyway, besides waiting for the periodic autosave, I found a way to manually trigger a save at any time: simply try to close the browser tab/window for that notebook. If you have unsaved changes, you will get a confirmation dialog asking you if you really want to leave, or stay. And it turns out, whichever one you choose, it will still save the notebook!
Hai Nguyen
Jul 1, 2016, 1:56:37 AM7/1/16
to jup...@googlegroups.com
On Thu, Jun 30, 2016 at 11:55 PM, Lawrence D’Oliveiro <lawren...@gmail.com> wrote:
One curious lack from the notebook interface is a function for saving the current notebook without creating a checkpoint as well. Personally I haven’t used the checkpointing function much. Maybe others will point out how useful it has been to them. :)
Anyway, besides waiting for the periodic autosave, I found a way to manually trigger a save at any time: simply try to close the browser tab/window for that notebook. If you have unsaved changes, you will get a confirmation dialog asking you if you really want to leave, or stay. And it turns out, whichever one you choose, it will still save the notebook
Ctrl-S is your friend
Hai
Lawrence D’Oliveiro
Jul 1, 2016, 2:52:43 AM7/1/16
to Project Jupyter
On Friday, July 1, 2016 at 5:56:37 PM UTC+12, Hai Nguyen wrote:
Ctrl-S is your friend
The docs say that does a checkpoint.
Thomas Kluyver
Jul 1, 2016, 4:05:36 AM7/1/16
to Project Jupyter
The checkpoint mechanism partly exists as an awkward workaround for having autosave without a full undo mechanism - if you accidentally delete something in a way that can't be undone, and it happens to autosave just then, you will still be able to get back to your last manual save. In this context, it makes sense that manual save implies checkpointing.
MinRK
Jul 1, 2016, 9:50:34 AM7/1/16
to Project Jupyter
It's fine to consider manual save via checkpoint equivalent to saving. Autosave will write the file more frequently, so the checkpoint is there for every 'manual' save, so that you can recover your last manually saved version if the autosave wrote a version you don't want to keep.
-MinRK
On Fri, Jul 1, 2016 at 10:05 AM, Thomas Kluyver <tak...@gmail.com> wrote:
The checkpoint mechanism partly exists as an awkward workaround for having autosave without a full undo mechanism - if you accidentally delete something in a way that can't be undone, and it happens to autosave just then, you will still be able to get back to your last manual save. In this context, it makes sense that manual save implies checkpointing.
--
You received this message because you are subscribed to the Google Groups "Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jupyter+u...@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAOvn4qgRZJdetDW33NqG9vOMG5VfbFkXabjJwmXqH6h59eRm3Q%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages