This PR addresses #106. When compilation is invoked and involves open dirty files, the user is asked whether to continue (ignoring the unsaved changes). Aborting the compilation allows the user to create a clean state and then invoke compilation again.
Refactorings are completely prevented if an open dirty file is involved.
Based on this branch, I added further preferences to control what is done during refactoring in a separate branch, just in case you want to try out those changes.
This PR addresses #106. When compilation is invoked and involves open dirty files, the user is asked whether to continue (ignoring the unsaved changes). Aborting the compilation allows the user to create a clean state and then invoke compilation again.
Refactorings are completely prevented if an open dirty file is involved.