This could be some kind of race condition/timing issue. I believe vim replaces the file entirely. The directory inspection might be too fast to catch the final state of the directory. I would expect it to run again after the new file has arrived, but that does not seem to happen.
However, even a future reinspection does not bring the file back into the tree. Something else is (more) wrong.
This could be some kind of race condition/timing issue. I believe
vimreplaces the file entirely. The directory inspection might be too fast to catch the final state of the directory. I would expect it to run again after the new file has arrived, but that does not seem to happen.However, even a future reinspection does not bring the file back into the tree. Something else is (more) wrong.