-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Unable to disable autosave in collaborative mode #14619
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
Unable to disable autosave in collaborative mode #14619
Comments
In collaborative mode it is not possible to disable auto-save. |
ohw, i thought it was available as a toggle.... so, as it currently stands, there's no way to:
right? ( this is behaviour in other editors. ) if yes, then any near future plans for that? |
I don't know if it makes sense to not auto-save in collaboration mode. A user might not want to save, but they cannot prevent other users to do so anyway. |
Yes but the extension may be installed in the current environment but not always be in used. So it makes sense to be able to turn off auto-save in collaboration mode; Microsoft office as a obvious toggle to do that for example: |
To summarize, there are two issues here:
|
one more reference of the implementation of the intended behaviour:
- https://www.geany.org/manual/current/#various-preferences:~:text=reload_clean_doc_on_file_change |
I think it is fair to allow users to disable auto-save and only save manually. Yes, there are caveats such that another user can save when in collaborative mode, but I think this is fine as long as it is documented and UI can display that the file was saved by someone else. I think the pattern is to enforce autosave in cloud-synced documents, not in collaborative documents; yes most collaborative documents are cloud-synced nowadays, but in cases where they are not, the user still has to deal with their file system limitations and auto-save can lead to inadvertent side-effects, for example if users have file system watch scripts, such as performing expensive anti-virus scans on each modification (which is sometimes enforced and user has no way to disable it). Technically, I think we only want to:
We may also want to:
|
continued from #14516
Description
Describe the bug clearly and concisely. Include screenshots if possible
The changes i am making are getting automatically saved always in jupyter lab 4 (all the --pre, 4.0, and 4.0.1)
despite having the option of "Autosave Documents < Settings" in jupyter lab turned off (shown as blank in the gutter)
vivaldi_Qz1RcIK5Nl.mp4
Reproduce
the unsaved indicating disc disappears (i.e. changes are saved to file) to be replaced by closing x
Expected behavior
file should not be autosaved
Context
Troubleshoot Output
Command Line Output
Browser Output
The text was updated successfully, but these errors were encountered: