Mercurial > vim
annotate runtime/doc/os_win32.txt @ 14518:f05e63d1d2e0
Added tag v8.1.0272 for changeset a28fb81c9ecf9cff9a89078266099fcc1d20f818
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Sat, 11 Aug 2018 18:00:06 +0200 |
parents | 2f7e67dd088c |
children | 4ee65b4150fd |
rev | line source |
---|---|
13963 | 1 *os_win32.txt* For Vim version 8.1. Last change: 2017 Mar 21 |
7 | 2 |
3 | |
4 VIM REFERENCE MANUAL by George Reilly | |
5 | |
6 | |
7 *win32* *Win32* *MS-Windows* | |
8 This file documents the idiosyncrasies of the Win32 version of Vim. | |
9 | |
10264
c036c0f636d5
commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
10 The Win32 version of Vim works on Windows XP, Vista, 7, 8 and 10. There are |
c036c0f636d5
commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
11 both console and GUI versions. |
2364
151b037b7e74
Fix hang when resizing in diff mode and there are concealed items.
Bram Moolenaar <bram@vim.org>
parents:
2345
diff
changeset
|
12 |
151b037b7e74
Fix hang when resizing in diff mode and there are concealed items.
Bram Moolenaar <bram@vim.org>
parents:
2345
diff
changeset
|
13 The 32 bit version also runs on 64 bit MS-Windows systems. |
151b037b7e74
Fix hang when resizing in diff mode and there are concealed items.
Bram Moolenaar <bram@vim.org>
parents:
2345
diff
changeset
|
14 |
7 | 15 1. Known problems |win32-problems| |
16 2. Startup |win32-startup| | |
17 3. Restore screen contents |win32-restore| | |
18 4. Using the mouse |win32-mouse| | |
10264
c036c0f636d5
commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
19 5. Running under Windows 95 |win32-win95| |
c036c0f636d5
commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
20 6. Running under Windows 3.1 |win32-win3.1| |
c036c0f636d5
commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
21 7. Win32 mini FAQ |win32-faq| |
7 | 22 |
23 Additionally, there are a number of common Win32 and DOS items: | |
24 File locations |dos-locations| | |
25 Using backslashes |dos-backslash| | |
26 Standard mappings |dos-standard-mappings| | |
27 Screen output and colors |dos-colors| | |
28 File formats |dos-file-formats| | |
29 :cd command |dos-:cd| | |
30 Interrupting |dos-CTRL-Break| | |
31 Temp files |dos-temp-files| | |
32 Shell option default |dos-shell| | |
33 | |
34 Win32 GUI |gui-w32| | |
35 | |
36 Credits: | |
37 The Win32 version was written by George V. Reilly <george@reilly.org>. | |
38 The original Windows NT port was done by Roger Knobbe <RogerK@wonderware.com>. | |
39 The GUI version was made by George V. Reilly and Robert Webb. | |
40 | |
2217
120502692d82
Improve the MS-Windows installer.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
41 For compiling see "src/INSTALLpc.txt". *win32-compiling* |
7 | 42 |
43 ============================================================================== | |
10264
c036c0f636d5
commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
44 1. Known problems *win32-problems* |
7 | 45 |
46 When doing file name completion, Vim also finds matches for the short file | |
47 name. But Vim will still find and use the corresponding long file name. For | |
48 example, if you have the long file name "this_is_a_test" with the short file | |
49 name "this_i~1", the command ":e *1" will start editing "this_is_a_test". | |
50 | |
51 ============================================================================== | |
52 2. Startup *win32-startup* | |
53 | |
54 Current directory *win32-curdir* | |
55 | |
56 If Vim is started with a single file name argument, and it has a full path | |
57 (starts with "x:\"), Vim assumes it was started from the file explorer and | |
58 will set the current directory to where that file is. To avoid this when | |
59 typing a command to start Vim, use a forward slash instead of a backslash. | |
60 Example: > | |
61 | |
62 vim c:\text\files\foo.txt | |
63 | |
64 Will change to the "C:\text\files" directory. > | |
65 | |
66 vim c:/text\files\foo.txt | |
67 | |
68 Will use the current directory. | |
69 | |
70 | |
71 Term option *win32-term* | |
72 | |
73 The only kind of terminal type that the Win32 version of Vim understands is | |
74 "win32", which is built-in. If you set 'term' to anything else, you will | |
75 probably get very strange behavior from Vim. Therefore Vim does not obtain | |
76 the default value of 'term' from the environment variable "TERM". | |
77 | |
819 | 78 $PATH *win32-PATH* |
79 | |
80 The directory of the Vim executable is appended to $PATH. This is mostly to | |
5400 | 81 make "!xxd" work, as it is in the Tools menu. And it also means that when |
819 | 82 executable() returns 1 the executable can actually be executed. |
83 | |
12756
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
84 Command line arguments *win32-cmdargs* |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
85 |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
86 Analysis of a command line into parameters is not standardised in MS Windows. |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
87 Vim and gvim used to use different logic to parse it (before 7.4.432), and the |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
88 logic was also depended on what it was compiled with. Now Vim and gvim both |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
89 use the CommandLineToArgvW() Win32 API, so they behave in the same way. |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
90 |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
91 The basic rules are: *win32-backslashes* |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
92 a) A parameter is a sequence of graphic characters. |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
93 b) Parameters are separated by white space. |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
94 c) A parameter can be enclosed in double quotes to include white space. |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
95 d) A sequence of zero or more backslashes (\) and a double quote (") |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
96 is special. The effective number of backslashes is halved, rounded |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
97 down. An even number of backslashes reverses the acceptability of |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
98 spaces and tabs, an odd number of backslashes produces a literal |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
99 double quote. |
8440
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
100 |
12756
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
101 So: |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
102 " is a special double quote |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
103 \" is a literal double quote |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
104 \\" is a literal backslash and a special double quote |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
105 \\\" is a literal backslash and a literal double quote |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
106 \\\\" is 2 literal backslashes and a special double quote |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
107 \\\\\" is 2 literal backslashes and a literal double quote |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
108 etc. |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
109 |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
110 Example: > |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
111 vim "C:\My Music\freude" +"set ignorecase" +/"\"foo\\" +\"bar\\\" |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
112 |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
113 opens "C:\My Music\freude" and executes the line mode commands: > |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
114 set ignorecase; /"foo\ and /bar\" |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
115 |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
116 These rules are also described in the reference of the CommandLineToArgvW API: |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
117 https://msdn.microsoft.com/en-us/library/windows/desktop/bb776391.aspx |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
118 |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
119 *win32-quotes* |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
120 There are additional rules for quotes (which are not well documented). |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
121 As described above, quotes inside a file name (or any other command line |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
122 argument) can be escaped with a backslash. E.g. > |
8440
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
123 vim -c "echo 'foo\"bar'" |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
124 |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
125 Alternatively use three quotes to get one: > |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
126 vim -c "echo 'foo"""bar'" |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
127 |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
128 The quotation rules are: |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
129 |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
130 1. A `"` starts quotation. |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
131 2. Another `"` or `""` ends quotation. If the quotation ends with `""`, a `"` |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
132 is produced at the end of the quoted string. |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
133 |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
134 Examples, with [] around an argument: |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
135 "foo" -> [foo] |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
136 "foo"" -> [foo"] |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
137 "foo"bar -> [foobar] |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
138 "foo" bar -> [foo], [bar] |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
139 "foo""bar -> [foo"bar] |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
140 "foo"" bar -> [foo"], [bar] |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
141 "foo"""bar" -> [foo"bar] |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
142 |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
6259
diff
changeset
|
143 |
7 | 144 ============================================================================== |
145 3. Restore screen contents *win32-restore* | |
146 | |
147 When 'restorescreen' is set (which is the default), Vim will restore the | |
148 original contents of the console when exiting or when executing external | |
149 commands. If you don't want this, use ":set nors". |'restorescreen'| | |
150 | |
151 ============================================================================== | |
152 4. Using the mouse *win32-mouse* | |
153 | |
154 The Win32 version of Vim supports using the mouse. If you have a two-button | |
155 mouse, the middle button can be emulated by pressing both left and right | |
156 buttons simultaneously - but note that in the Win32 GUI, if you have the right | |
157 mouse button pop-up menu enabled (see 'mouse'), you should err on the side of | |
158 pressing the left button first. |mouse-using| | |
159 | |
160 When the mouse doesn't work, try disabling the "Quick Edit Mode" feature of | |
161 the console. | |
162 | |
163 ============================================================================== | |
10264
c036c0f636d5
commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
164 5. Running under Windows 95 *win32-win95* |
c036c0f636d5
commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
165 *windows95* *windows98* *windowsme* |
c036c0f636d5
commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
166 Windows 95/98/ME support was removed in patch 8.0.0029 If you want to use it |
c036c0f636d5
commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
167 you will need to get a version older than that. |
7 | 168 |
10264
c036c0f636d5
commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
169 ============================================================================== |
c036c0f636d5
commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
170 6. Running under Windows 3.1 *win32-win3.1* |
c036c0f636d5
commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
171 |
14123 | 172 *win32s* *windows-3.1* *gui-w32s* *win16* |
11473 | 173 There was a special version of gvim that runs under Windows 3.1 and 3.11. |
10048
43efa4f5a8ea
commit https://github.com/vim/vim/commit/89bcfda6834aba724d12554a34b9ed49f5789fd5
Christian Brabandt <cb@256bit.org>
parents:
8440
diff
changeset
|
174 Support was removed in patch 7.4.1363. |
7 | 175 |
176 ============================================================================== | |
10264
c036c0f636d5
commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
177 7. Win32 mini FAQ *win32-faq* |
7 | 178 |
179 Q. How do I change the font? | |
22 | 180 A. In the GUI version, you can use the 'guifont' option. Example: > |
181 :set guifont=Lucida_Console:h15:cDEFAULT | |
182 < In the console version, you need to set the font of the console itself. | |
7 | 183 You cannot do this from within Vim. |
184 | |
185 Q. How do I type dead keys on Windows NT? | |
186 A. Dead keys work on NT 3.51. Just type them as you would in any other | |
187 application. | |
188 On NT 4.0, you need to make sure that the default locale (set in the | |
189 Keyboard part of the Control Panel) is the same as the currently active | |
190 locale. Otherwise the NT code will get confused and crash! This is a NT | |
191 4.0 problem, not really a Vim problem. | |
192 | |
193 Q. I'm using Vim to edit a symbolically linked file on a Unix NFS file server. | |
194 When I write the file, Vim does not "write through" the symlink. Instead, | |
195 it deletes the symbolic link and creates a new file in its place. Why? | |
196 A. On Unix, Vim is prepared for links (symbolic or hard). A backup copy of | |
197 the original file is made and then the original file is overwritten. This | |
198 assures that all properties of the file remain the same. On non-Unix | |
199 systems, the original file is renamed and a new file is written. Only the | |
200 protection bits are set like the original file. However, this doesn't work | |
201 properly when working on an NFS-mounted file system where links and other | |
202 things exist. The only way to fix this in the current version is not | |
203 making a backup file, by ":set nobackup nowritebackup" |'writebackup'| | |
204 | |
22 | 205 Q. I'm using Vim to edit a file on a Unix file server through Samba. When I |
206 write the file, the owner of the file is changed. Why? | |
207 A. When writing a file Vim renames the original file, this is a backup (in | |
208 case writing the file fails halfway). Then the file is written as a new | |
209 file. Samba then gives it the default owner for the file system, which may | |
210 differ from the original owner. | |
211 To avoid this set the 'backupcopy' option to "yes". Vim will then make a | |
212 copy of the file for the backup, and overwrite the original file. The | |
213 owner isn't changed then. | |
214 | |
7 | 215 Q. How do I get to see the output of ":make" while it's running? |
216 A. Basically what you need is to put a tee program that will copy its input | |
217 (the output from make) to both stdout and to the errorfile. You can find a | |
1125 | 218 copy of tee (and a number of other GNU tools) at |
7 | 219 http://gnuwin32.sourceforge.net or http://unxutils.sourceforge.net |
220 Alternatively, try the more recent Cygnus version of the GNU tools at | |
221 http://www.cygwin.com Other Unix-style tools for Win32 are listed at | |
222 http://directory.google.com/Top/Computers/Software/Operating_Systems/Unix/Win32/ | |
223 When you do get a copy of tee, you'll need to add > | |
224 :set shellpipe=\|\ tee | |
225 < to your _vimrc. | |
226 | |
227 Q. I'm storing files on a remote machine that works with VisionFS, and files | |
228 disappear! | |
229 A. VisionFS can't handle certain dot (.) three letter extension file names. | |
230 SCO declares this behavior required for backwards compatibility with 16bit | |
231 DOS/Windows environments. The two commands below demonstrate the behavior: | |
232 > | |
233 echo Hello > file.bat~ | |
234 dir > file.bat | |
235 < | |
236 The result is that the "dir" command updates the "file.bat~" file, instead | |
237 | 237 of creating a new "file.bat" file. This same behavior is exhibited in Vim |
7 | 238 when editing an existing file named "foo.bat" because the default behavior |
239 of Vim is to create a temporary file with a '~' character appended to the | |
240 name. When the file is written, it winds up being deleted. | |
241 | |
242 Solution: Add this command to your _vimrc file: > | |
243 :set backupext=.temporary | |
244 | |
245 Q. How do I change the blink rate of the cursor? | |
246 A. You can't! This is a limitation of the NT console. NT 5.0 is reported to | |
247 be able to set the blink rate for all console windows at the same time. | |
248 | |
249 *:!start* | |
11230
a3ea65af63cf
patch 8.0.0501: on MS-Windows ":!start" does not work as expected
Christian Brabandt <cb@256bit.org>
parents:
10264
diff
changeset
|
250 Q. How can I asynchronously run an external command or program, or open a |
a3ea65af63cf
patch 8.0.0501: on MS-Windows ":!start" does not work as expected
Christian Brabandt <cb@256bit.org>
parents:
10264
diff
changeset
|
251 document or URL with its default program? |
a3ea65af63cf
patch 8.0.0501: on MS-Windows ":!start" does not work as expected
Christian Brabandt <cb@256bit.org>
parents:
10264
diff
changeset
|
252 A. When using :! to run an external command, you can run it with "start". For |
a3ea65af63cf
patch 8.0.0501: on MS-Windows ":!start" does not work as expected
Christian Brabandt <cb@256bit.org>
parents:
10264
diff
changeset
|
253 example, to run notepad: > |
a3ea65af63cf
patch 8.0.0501: on MS-Windows ":!start" does not work as expected
Christian Brabandt <cb@256bit.org>
parents:
10264
diff
changeset
|
254 :!start notepad |
a3ea65af63cf
patch 8.0.0501: on MS-Windows ":!start" does not work as expected
Christian Brabandt <cb@256bit.org>
parents:
10264
diff
changeset
|
255 < To open "image.jpg" with the default image viewer: > |
a3ea65af63cf
patch 8.0.0501: on MS-Windows ":!start" does not work as expected
Christian Brabandt <cb@256bit.org>
parents:
10264
diff
changeset
|
256 :!start image.jpg |
a3ea65af63cf
patch 8.0.0501: on MS-Windows ":!start" does not work as expected
Christian Brabandt <cb@256bit.org>
parents:
10264
diff
changeset
|
257 < To open the folder of the current file in Windows Explorer: > |
a3ea65af63cf
patch 8.0.0501: on MS-Windows ":!start" does not work as expected
Christian Brabandt <cb@256bit.org>
parents:
10264
diff
changeset
|
258 :!start %:h |
a3ea65af63cf
patch 8.0.0501: on MS-Windows ":!start" does not work as expected
Christian Brabandt <cb@256bit.org>
parents:
10264
diff
changeset
|
259 < To open the Vim home page with the default browser: > |
a3ea65af63cf
patch 8.0.0501: on MS-Windows ":!start" does not work as expected
Christian Brabandt <cb@256bit.org>
parents:
10264
diff
changeset
|
260 :!start http://www.vim.org/ |
a3ea65af63cf
patch 8.0.0501: on MS-Windows ":!start" does not work as expected
Christian Brabandt <cb@256bit.org>
parents:
10264
diff
changeset
|
261 < |
a3ea65af63cf
patch 8.0.0501: on MS-Windows ":!start" does not work as expected
Christian Brabandt <cb@256bit.org>
parents:
10264
diff
changeset
|
262 Using "start" stops Vim switching to another screen, opening a new console, |
7 | 263 or waiting for the program to complete; it indicates that you are running a |
1624 | 264 program that does not affect the files you are editing. Programs begun |
7 | 265 with :!start do not get passed Vim's open file handles, which means they do |
266 not have to be closed before Vim. | |
267 To avoid this special treatment, use ":! start". | |
2859 | 268 There are two optional arguments (see the next Q): |
3513 | 269 /min the window will be minimized |
270 /b no console window will be opened | |
3082 | 271 You can use only one of these flags at a time. A second one will be |
2859 | 272 treated as the start of the command. |
273 | |
274 Q. How do I avoid getting a window for programs that I run asynchronously? | |
3082 | 275 A. You have two possible solutions depending on what you want: |
2908 | 276 1) You may use the /min flag in order to run program in a minimized state |
277 with no other changes. It will work equally for console and GUI | |
278 applications. | |
279 2) You can use the /b flag to run console applications without creating a | |
2859 | 280 console window for them (GUI applications are not affected). But you |
2908 | 281 should use this flag only if the application you run doesn't require any |
282 input. Otherwise it will get an EOF error because its input stream | |
3082 | 283 (stdin) would be redirected to \\.\NUL (stdout and stderr too). |
2859 | 284 |
285 Example for a console application, run Exuberant ctags: > | |
286 :!start /min ctags -R . | |
287 < When it has finished you should see file named "tags" in your current | |
288 directory. You should notice the window title blinking on your taskbar. | |
6180 | 289 This is more noticeable for commands that take longer. |
2859 | 290 Now delete the "tags" file and run this command: > |
291 :!start /b ctags -R . | |
292 < You should have the same "tags" file, but this time there will be no | |
293 blinking on the taskbar. | |
294 Example for a GUI application: > | |
295 :!start /min notepad | |
296 :!start /b notepad | |
297 < The first command runs notepad minimized and the second one runs it | |
298 normally. | |
7 | 299 |
6259 | 300 *windows-icon* |
301 Q. I don't like the Vim icon, can I change it? | |
302 A. Yes, place your favorite icon in bitmaps/vim.ico in a directory of | |
303 'runtimepath'. For example ~/vimfiles/bitmaps/vim.ico. | |
304 | |
305 | |
14421 | 306 vim:tw=78:fo=tcq2:ts=8:noet:ft=help:norl: |