Mike Williams wrote:
> On 28 Jun 2004 at 11:56, BamseIsUnix wrote:
>>Again. Vim jammed completely and after about 10 seconds the file was
>>"changed" and when reloaded, appeared blank. If I clicked "Ok" in that
>>dialog box, same thing happened as with "Reload". It's blank.
> I assume this description is not from when doing the above echo but
> reading a file into VIM.
>>But just few seconds ago it happened once again I tried another way. I
>>*killed* Vim right away when, upon opening a file, it quit responding. I
>>had to wait for some seconds that Vim went away and after that, opened
>>the file again. It wasn't blank. So the file is destroyed -after- Vim
>>Is Vim destroying our files?
> Based on 10 years use on a variety of machines and networks I would say
> no. It will be due to interaction of other things outside the control
> of VIM, such as the version of Samba.
> You say these are active web pages - in that they are being served to
> the net at the same time you are editing them. They are not being
> dynamically generated are they? Does it happen for all files all the
> time? Or is it seemingly at random (i.e. any file at any time may or
> may not have a problem)?
> Pure guesswork but it may be an interaction between VIM accessing the
> file and the web server serving it up.
> I've lost the thread so can't remember if you have tried the following
> test - can you create a file somewhere else on the same machine that
> you can guarantee that the server wont access and edit that without
> If you are not able to experiment with the variables (network, OS,
> Samba, directories, etc.) then the safest bet is to keep local copies
> of the files you are editing and copy them to the server when you are
> happy with the edits.
Yeah well I don't believe it's Vim. At home I have it as my default text
editor, it has never failed me and it never will.
It is something to do with the network mapping, it has to be. Or the web
server working simultaneously as you suggested. The problem is
completely random. Happens with any file, at any time. It happened today
only twice, though (out of 8 hours of editing).
So it's not Vim. Then it must happen with any other editor. I haven't
tested. Why should I, it's not a problem anymore because it isn't Vim.
:) We do keep backups ("~" files).