diff options
| author | Bram Moolenaar <Bram@vim.org> | 2004-09-02 19:12:26 +0000 |
|---|---|---|
| committer | Bram Moolenaar <Bram@vim.org> | 2004-09-02 19:12:26 +0000 |
| commit | d4755bb0e04fca334675f1503bd6474b017a9bba (patch) | |
| tree | 8be8df859191e78ee9eef80d3b341fd5d0c1b81b /runtime/doc/os_msdos.txt | |
| parent | 269ec658f0fad22b2bf9f71b06a4e6e10277f0e5 (diff) | |
| download | vim-d4755bb0e04fca334675f1503bd6474b017a9bba.zip | |
updated for version 7.0014
Diffstat (limited to 'runtime/doc/os_msdos.txt')
| -rw-r--r-- | runtime/doc/os_msdos.txt | 24 |
1 files changed, 15 insertions, 9 deletions
diff --git a/runtime/doc/os_msdos.txt b/runtime/doc/os_msdos.txt index 01290e9ff..3c749f0eb 100644 --- a/runtime/doc/os_msdos.txt +++ b/runtime/doc/os_msdos.txt @@ -1,4 +1,4 @@ -*os_msdos.txt* For Vim version 7.0aa. Last change: 2001 Sep 03 +*os_msdos.txt* For Vim version 7.0aa. Last change: 2004 Aug 31 VIM REFERENCE MANUAL by Bram Moolenaar @@ -207,18 +207,24 @@ in such a way that it becomes too long may give unexpected results. 8. Symbolically linked files *msdos-linked-files* When using Vim to edit a symbolically linked file on a unix NFS file server, -you may run into problems. -When writing the file, Vim does not "write through" the symlink. Instead, it -deletes the symbolic link and creates a new file in its place. - 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 +you may run into problems. When writing the file, Vim does not "write +through" the symlink. Instead, it deletes the symbolic link and creates a new +file in its place. + +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'| +A similar problem occurs when mounting a Unix filesystem through Samba or a +similar system. When Vim creates a new file it will get the default user ID +for the mounted file system. This may be different from the original user ID. +To avoid this set the 'backupcopy' option to "yes". + ============================================================================== 9. Copy/paste in a dos box *msdos-copy-paste* |