Front page | perl.perl5.porters |
Postings from May 2003
On Wed, 14 May 2003 14:27:46 PDT, Edward Peschko wrote: >Of course, it could be that gvim is somehow unlinking the file, and then re-e >diting it... >that would be exceedingly dumb (especially for an editor) but possible. This is "normal" behavior for vim. From the vim 5.6 docs: : On Unix, Vim is prepared for links (symbolic or hard). A backup copy of :the original file is made and then the original file is overwritten. This :assures that all properties of the file remain the same. On non-Unix systems, :the original file is renamed and a new file is written. Only the protection :bits are set like the original file. However, this doesn't work properly when :working on an NFS-mounted file system where links and other things exist. The :only way to fix this in the current version is not making a backup file, by :":set nobackup nowritebackup" |'writebackup'| Newer versions of vim are better--you can control the behavior with the 'backupcopy' option. Sarathy gsar@ActiveState.comThread Previous | Thread Next