-
Notifications
You must be signed in to change notification settings - Fork 28.4k
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
External file watcher fails for editors that do atomic saves #15111
Comments
Please see if you can find any logged output that could help us find the source of the issue:
Thanks! |
I did that and this is the output: I've replicated exactly what I told above. Including the save in vscode after edited the file with external application, thats why the RED text appeared. Full log here: |
@jzeferino and your settings? |
@bpasero vscode settings? Or other settings? |
@jzeferino yeah your vscode settings.json (and if you have workspace settings in the .vscode folder). I wonder if you maybe configured the file watcher exclude rules. |
@bpasero settings.json is empty and I didn't configured the file watcher exclude rules. |
I can reproduce and it is caused by the fact that TextEdit saves the file by first renaming it to another file (something that is called atomic save). The node file watcher we are using is probably stopping to watch at that time and gets disposed. |
I have an idea how to fix 👍 |
Good work. I was testing in on windows and it works good. There is any way to get a popup when the file is changed via external editor? Could I define it via settings? |
No, that is not supported atm. |
Steps to Reproduce:
side note: after editing the file in vscode and try to save it, and it shows a upper popup telling that the file has some diferences from the original and open a compare window.
The text was updated successfully, but these errors were encountered: