When I have atom open it apparently stays in the current directory of a file that is open so that the directory is locked and cannot be delete (under Windows).
Lets say I a maven project that generates and stores adoc files in a directory project/target/docs/adoc/file.adoc
When I open the adoc directory to view and edit the file, running mvn clean fails since the directory project/target cannot be deleted (its locked by Windows due to atom).
It would be better to either implement the file update check in a way that doesn’t stay in the directory or to have an option to disable the file checks or to disable the file checks when the editor window isn’t in front.
I am currently using atom 0.199.0 in Windows 7 64 with the asciidoc preview plugin.
Edit: I have verified the same operation with Eclipse in Windows (i.e. keeping a file open and running maven in another window and it looks like Eclipse is doing the file change check if the Eclipse window is coming to the foreground so that the file or directory is not locked most of the time.