Autosave limitations and possible issues Follow
Hi there,
I know that many have discussed about this topic. However, I still have some questions concerning it.
1. It is very possible to open files outside of the open project (i.e. other txt, xml files). You can also edit them by mistake, close their tab and lose the track of changes (suppose they are not under version control).
2. It happened that I opened the threading.py module, changed it by mistake, and lost track of the edit. I was testing different characteristics of the editor ... Anyway, this is a another example on how it can do harm sometimes.
Thanks for time,
Sebi
I know that many have discussed about this topic. However, I still have some questions concerning it.
1. It is very possible to open files outside of the open project (i.e. other txt, xml files). You can also edit them by mistake, close their tab and lose the track of changes (suppose they are not under version control).
- How can I get their local history?
- Is there a way to access the full history as logged for all external files? The only way I could find is to open it (first to remember it), right click on tab and open the local history?
2. It happened that I opened the threading.py module, changed it by mistake, and lost track of the edit. I was testing different characteristics of the editor ... Anyway, this is a another example on how it can do harm sometimes.
- Is any way to protect external files, outside of the current project, of being auto-saved?
- Again, is it a way to see the global local history.
- Besides recently changed files, is there any other safe mechanism of tracking the changed files?
Thanks for time,
Sebi
Please sign in to leave a comment.
We plan to make it more difficult to accidentally modify library files (such as files in the Python standard library).