Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs / file menu: explain how to exit the notebook #3153

Closed
timmie opened this issue Apr 9, 2013 · 15 comments
Closed

docs / file menu: explain how to exit the notebook #3153

timmie opened this issue Apr 9, 2013 · 15 comments
Assignees
Milestone

Comments

@timmie
Copy link

timmie commented Apr 9, 2013

The Notebook page is still very basic.

A issue that always confuses me and resulted in data loss today:

How to I quit a notebook saving my work?

File -> Close and Halt
==> Kernel apparently stopped and all data lost!

File -> Save
==> Work saves but notebook still active.

What I miss:

File -> Exit (halt) saving changes.

Or better:
When I exit (halt) a pop-up:
"Do you want to save or discard the changes.

@timmie
Copy link
Author

timmie commented Apr 9, 2013

see also: #1378

@timmie
Copy link
Author

timmie commented Apr 9, 2013

IPython.__version__
Out[3]:

'0.13.1'

@timmie
Copy link
Author

timmie commented Apr 9, 2013

Is it OK?
Seems I mix 2 things here.

@minrk
Copy link
Member

minrk commented Apr 15, 2013

There is a dialog if you try to navigate away from a page with unsaved changes (this includes closing with ^W or Close & Halt or just Close) - if this is not occurring, there is a bug in the detection of changes (the dirty flag in the notebook), and may have since been fixed in master.

In general, this will probably be addressed by #3158, since it will become impossible to close the notebook page without saving changes (to the autosave file, at least).

@timmie
Copy link
Author

timmie commented Apr 29, 2013

There is a dialog if you try to navigate away from a page with unsaved changes (this includes closing with ^W or Close & Halt or just Close)

Yes, but it still does not tell what to do to save the whole stuff.

Why not be a bit clear for the not-so-every-day user:

File -> Exit (halt) saving changes.

or

When I exit (halt) a pop-up:
"Do you want to save or discard the changes? YES/NO"

It would add more usability.

@minrk
Copy link
Member

minrk commented Apr 29, 2013

After PR #3158, it will save changes. It will no longer be possible to discard changes.

@timmie
Copy link
Author

timmie commented Apr 29, 2013

Well, I was just trying to suggest a more intuitive wording for the dialogues/menus.

But if it's a won't fix then feel free to close.

@minrk
Copy link
Member

minrk commented Apr 29, 2013

Sorry, I mainly mean that what wording is most appropriate will change, since with autosave there won't ever be unsaved changes for the user to make decisions about.

@ghost ghost assigned ivanov Jul 13, 2013
@ivanov
Copy link
Member

ivanov commented Jul 13, 2013

this one's been tagged as "docs" so i'll tackle it

@ellisonbg
Copy link
Member

I think the current behavior is fine, @ivanov are you ok if we close this?

@minrk
Copy link
Member

minrk commented Jan 27, 2014

@ellisonbg this is marked as a docs issue, not a bug in behavior.

@timmie
Copy link
Author

timmie commented Jan 27, 2014

@minrk

It was an issue before the auto-save was implemented -- at that point it was not clear how to exit & save..

Can be closed at all.

@timmie timmie closed this as completed Jan 27, 2014
@ellisonbg
Copy link
Member

@minrk what I meant was that I think that now that we have autosave, there isn't any significant confusion about what the "Close and Halt" menu item does that needs documentation.

@ivanov
Copy link
Member

ivanov commented Jan 27, 2014

At some point I also added this title="Shutdown this notebook's kernel, and close this window" to that menu item, as well, which appears on hover over the menu item in most browsers, so I think we're all good here. (67cd531 was the commit)

@minrk
Copy link
Member

minrk commented Jan 27, 2014

Thanks for clarifying. Makes sense to me now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants