summaryrefslogtreecommitdiffstats
path: root/runtime/doc/os_win32.txt
diff options
context:
space:
mode:
Diffstat (limited to 'runtime/doc/os_win32.txt')
-rw-r--r--runtime/doc/os_win32.txt17
1 files changed, 14 insertions, 3 deletions
diff --git a/runtime/doc/os_win32.txt b/runtime/doc/os_win32.txt
index 29d7096bf4..6f9a541c2e 100644
--- a/runtime/doc/os_win32.txt
+++ b/runtime/doc/os_win32.txt
@@ -1,4 +1,4 @@
-*os_win32.txt* For Vim version 7.0aa. Last change: 2004 May 01
+*os_win32.txt* For Vim version 7.0aa. Last change: 2004 Aug 31
VIM REFERENCE MANUAL by George Reilly
@@ -184,8 +184,9 @@ A. There are no good reasons to run the 16-bit DOS version on NT. The Win32
runs on top of an 80x86 emulator.
Q. How do I change the font?
-A. In the GUI version, you can use the 'guifont' option.
- In the console version, you need to set the font of the console itself.
+A. In the GUI version, you can use the 'guifont' option. Example: >
+ :set guifont=Lucida_Console:h15:cDEFAULT
+< In the console version, you need to set the font of the console itself.
You cannot do this from within Vim.
Q. When I change the size of the console window with ':set lines=xx' or
@@ -249,6 +250,16 @@ A. On Unix, Vim is prepared for links (symbolic or hard). A backup copy of
things exist. The only way to fix this in the current version is not
making a backup file, by ":set nobackup nowritebackup" |'writebackup'|
+Q. I'm using Vim to edit a file on a Unix file server through Samba. When I
+ write the file, the owner of the file is changed. Why?
+A. When writing a file Vim renames the original file, this is a backup (in
+ case writing the file fails halfway). Then the file is written as a new
+ file. Samba then gives it the default owner for the file system, which may
+ differ from the original owner.
+ To avoid this set the 'backupcopy' option to "yes". Vim will then make a
+ copy of the file for the backup, and overwrite the original file. The
+ owner isn't changed then.
+
Q. How do I get to see the output of ":make" while it's running?
A. Basically what you need is to put a tee program that will copy its input
(the output from make) to both stdout and to the errorfile. You can find a