Comment 2 for bug 1123267

When reporting the bug I was writing C++ code. I simply launched the GNU C++ compiler after changing something on the code and ran into this error. I am writing with a two-pane Terminator terminal emulation and I am able to switch fast enough to the terminal on the right side, start the compiliation and trigger this error.

It is clear that the file does vanishes for a very short amount of time using my VIM settings, but it should be back after a few microseconds. Right now I'm able to trigger this error by hand which is quite troubling.

I was already trying to write some test cow which could show this behavior. So far it looks like VIM performs a series of operations in the filesystem. It does not move the original version directly to ~/.vimbackup but first renames the file as filename~. Then it creates the new version of the file and moves the filename~ backup file into ~/.vimbackup.

I really wonder why the simple test case "mv test test.bak ; touch test" never shows this behavior.