Opening a notebook causes an unsaved state? #12817
Unanswered
JPvRiel
asked this question in
Questions and Answers
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It's driving me nuts that notebooks, even if just opened to read and refer to it, without re-running any cells or making any changes, it often seems to have unsaved changes.
I'm a bit confused as to why, whenever I seem to simply just open and read, but not change a Jupyter notebook, vscode shows it's in an unsaved state. It's a headache because then, when I save it, functionally, the notebook has not changed at all. E.g. the user made no changes.
However, if I save it regardless of making changes, and compare a previous file copy to the I notice that each cell seems to have added language metadata to every cell. E.g. left is new saved version, right old version opened for reading only.
Perhaps recent changes in vscode have caused this
metadata
stuff, so any older notebook is always going to show it has unsaved changes even when the user made no changes?Beta Was this translation helpful? Give feedback.
All reactions