You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you rename a notebook from the filesystem (e.g. making copies of a template to fill out), the notebook list view shows it by the new filename. But when it's opened, it reads the name embedded in the notebook, and will save as that (e.g. template.ipynb), while deleting the new file (A.ipynb).
The text was updated successfully, but these errors were encountered:
Yup, agreed. Having files which can only be renamed with a custom tool is in general a bad idea, as it makes it impossible to automate many workflows. @ellisonbg, I think you had something in mind when deciding to add this behavior; thoughts?
I will have to refresh my thinking about this. I seem to have a vague recollection that it made more sense to go with the name embedded in the notebook file to resolve this conflict...but I don't remember why right now.
If you rename a notebook from the filesystem (e.g. making copies of a template to fill out), the notebook list view shows it by the new filename. But when it's opened, it reads the name embedded in the notebook, and will save as that (e.g.
template.ipynb
), while deleting the new file (A.ipynb
).The text was updated successfully, but these errors were encountered: