On Oct 26, 2:12 pm, Bram Moolenaar <[email protected]> wrote:
> Arve Knudsen wrote:
> > This is indeed a local filesystem (my C: drive). So far I've only seen
> > this with an x64 build, but I have installed this package before
> > without any such problems. As to reproducing it, I just edit a file
> > for a while, and then "4913" appears (after a minute perhaps). Funny
> > though, when I try to reproduce it right now, nothing happens. I was
> > able to make it happen earlier with a _vimrc only containing "set
> > nocompatible".
>
> Isn't it a caching problem? I can imagine that when you look at the
> file system at the right moment the file is there. If this view isn't
> updated for a little while you see the file, even though Vim has already
> deleted it.
>
> It's hard to imagine the file is properly deleted one moment and hangs
> around another time. Either something essential changed or it's flaky.
It appears that these files aren't deleted as they should, since they
hang around after Vim has been closed. I have reinstalled Windows now,
I'll see if the problem has gone away (current theory is my filesystem
was flaky).
Arve
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
