annotate runtime/doc/os_win32.txt @ 12084:69ce6b3f0834 v8.0.0922

patch 8.0.0922: quickfix list always added after current one commit https://github.com/vim/vim/commit/55b6926450d75788dada3ff44a35e328224df758 Author: Bram Moolenaar <Bram@vim.org> Date: Sun Aug 13 13:42:01 2017 +0200 patch 8.0.0922: quickfix list always added after current one Problem: Quickfix list always added after current one. Solution: Make it possible to add a quickfix list after the last one. (Yegappan Lakshmanan)
author Christian Brabandt <cb@256bit.org>
date Sun, 13 Aug 2017 13:45:04 +0200
parents bd6ff5246c71
children 3b26420fc639
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
rev   line source
11262
214f228718cf Update runtime files.
Christian Brabandt <cb@256bit.org>
parents: 11230
diff changeset
1 *os_win32.txt* For Vim version 8.0. Last change: 2017 Mar 21
7
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
2
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
3
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
4 VIM REFERENCE MANUAL by George Reilly
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
5
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
6
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
7 *win32* *Win32* *MS-Windows*
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
8 This file documents the idiosyncrasies of the Win32 version of Vim.
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
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
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
15 1. Known problems |win32-problems|
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
16 2. Startup |win32-startup|
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
17 3. Restore screen contents |win32-restore|
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
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
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
22
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
23 Additionally, there are a number of common Win32 and DOS items:
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
24 File locations |dos-locations|
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
25 Using backslashes |dos-backslash|
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
26 Standard mappings |dos-standard-mappings|
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
27 Screen output and colors |dos-colors|
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
28 File formats |dos-file-formats|
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
29 :cd command |dos-:cd|
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
30 Interrupting |dos-CTRL-Break|
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
31 Temp files |dos-temp-files|
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
32 Shell option default |dos-shell|
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
33
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
34 Win32 GUI |gui-w32|
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
35
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
36 Credits:
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
37 The Win32 version was written by George V. Reilly <george@reilly.org>.
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
38 The original Windows NT port was done by Roger Knobbe <RogerK@wonderware.com>.
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
39 The GUI version was made by George V. Reilly and Robert Webb.
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
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
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
42
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
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
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
45
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
46 When doing file name completion, Vim also finds matches for the short file
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
47 name. But Vim will still find and use the corresponding long file name. For
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
48 example, if you have the long file name "this_is_a_test" with the short file
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
49 name "this_i~1", the command ":e *1" will start editing "this_is_a_test".
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
50
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
51 ==============================================================================
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
52 2. Startup *win32-startup*
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
53
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
54 Current directory *win32-curdir*
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
55
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
56 If Vim is started with a single file name argument, and it has a full path
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
57 (starts with "x:\"), Vim assumes it was started from the file explorer and
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
58 will set the current directory to where that file is. To avoid this when
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
59 typing a command to start Vim, use a forward slash instead of a backslash.
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
60 Example: >
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
61
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
62 vim c:\text\files\foo.txt
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
63
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
64 Will change to the "C:\text\files" directory. >
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
65
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
66 vim c:/text\files\foo.txt
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
67
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
68 Will use the current directory.
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
69
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
70
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
71 Term option *win32-term*
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
72
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
73 The only kind of terminal type that the Win32 version of Vim understands is
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
74 "win32", which is built-in. If you set 'term' to anything else, you will
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
75 probably get very strange behavior from Vim. Therefore Vim does not obtain
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
76 the default value of 'term' from the environment variable "TERM".
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
77
819
23f82b5d2814 updated for version 7.0c10
vimboss
parents: 810
diff changeset
78 $PATH *win32-PATH*
23f82b5d2814 updated for version 7.0c10
vimboss
parents: 810
diff changeset
79
23f82b5d2814 updated for version 7.0c10
vimboss
parents: 810
diff changeset
80 The directory of the Vim executable is appended to $PATH. This is mostly to
5400
173c9c860e42 Runtime file updates.
Bram Moolenaar <bram@vim.org>
parents: 5294
diff changeset
81 make "!xxd" work, as it is in the Tools menu. And it also means that when
819
23f82b5d2814 updated for version 7.0c10
vimboss
parents: 810
diff changeset
82 executable() returns 1 the executable can actually be executed.
23f82b5d2814 updated for version 7.0c10
vimboss
parents: 810
diff changeset
83
8440
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
84 Quotes in file names *win32-quotes*
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
85
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
86 Quotes inside a file name (or any other command line argument) can be escaped
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
87 with a backslash. E.g. >
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
88 vim -c "echo 'foo\"bar'"
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
89
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
90 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
91 vim -c "echo 'foo"""bar'"
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
92
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
93 The quotation rules are:
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
94
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
95 1. A `"` starts quotation.
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
96 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
97 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
98
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
99 Examples, with [] around an argument:
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
100 "foo" -> [foo]
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
101 "foo"" -> [foo"]
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
102 "foo"bar -> [foobar]
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
103 "foo" bar -> [foo], [bar]
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
104 "foo""bar -> [foo"bar]
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
105 "foo"" bar -> [foo"], [bar]
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
106 "foo"""bar" -> [foo"bar]
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
107
4c6ad81d41fe commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents: 6259
diff changeset
108
7
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
109 ==============================================================================
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
110 3. Restore screen contents *win32-restore*
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
111
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
112 When 'restorescreen' is set (which is the default), Vim will restore the
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
113 original contents of the console when exiting or when executing external
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
114 commands. If you don't want this, use ":set nors". |'restorescreen'|
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
115
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
116 ==============================================================================
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
117 4. Using the mouse *win32-mouse*
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
118
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
119 The Win32 version of Vim supports using the mouse. If you have a two-button
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
120 mouse, the middle button can be emulated by pressing both left and right
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
121 buttons simultaneously - but note that in the Win32 GUI, if you have the right
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
122 mouse button pop-up menu enabled (see 'mouse'), you should err on the side of
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
123 pressing the left button first. |mouse-using|
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
124
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
125 When the mouse doesn't work, try disabling the "Quick Edit Mode" feature of
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
126 the console.
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
127
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
128 ==============================================================================
10264
c036c0f636d5 commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents: 10198
diff changeset
129 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
130 *windows95* *windows98* *windowsme*
c036c0f636d5 commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents: 10198
diff changeset
131 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
132 you will need to get a version older than that.
7
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
133
10264
c036c0f636d5 commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents: 10198
diff changeset
134 ==============================================================================
c036c0f636d5 commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents: 10198
diff changeset
135 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
136
c036c0f636d5 commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents: 10198
diff changeset
137 *win32s* *windows-3.1* *gui-w32s*
11473
bd6ff5246c71 Update runtime files.
Christian Brabandt <cb@256bit.org>
parents: 11262
diff changeset
138 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
139 Support was removed in patch 7.4.1363.
7
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
140
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
141 ==============================================================================
10264
c036c0f636d5 commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents: 10198
diff changeset
142 7. Win32 mini FAQ *win32-faq*
7
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
143
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
144 Q. How do I change the font?
22
cc049b00ee70 updated for version 7.0014
vimboss
parents: 7
diff changeset
145 A. In the GUI version, you can use the 'guifont' option. Example: >
cc049b00ee70 updated for version 7.0014
vimboss
parents: 7
diff changeset
146 :set guifont=Lucida_Console:h15:cDEFAULT
cc049b00ee70 updated for version 7.0014
vimboss
parents: 7
diff changeset
147 < In the console version, you need to set the font of the console itself.
7
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
148 You cannot do this from within Vim.
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
149
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
150 Q. How do I type dead keys on Windows NT?
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
151 A. Dead keys work on NT 3.51. Just type them as you would in any other
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
152 application.
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
153 On NT 4.0, you need to make sure that the default locale (set in the
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
154 Keyboard part of the Control Panel) is the same as the currently active
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
155 locale. Otherwise the NT code will get confused and crash! This is a NT
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
156 4.0 problem, not really a Vim problem.
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
157
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
158 Q. I'm using Vim to edit a symbolically linked file on a Unix NFS file server.
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
159 When I write the file, Vim does not "write through" the symlink. Instead,
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
160 it deletes the symbolic link and creates a new file in its place. Why?
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
161 A. On Unix, Vim is prepared for links (symbolic or hard). A backup copy of
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
162 the original file is made and then the original file is overwritten. This
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
163 assures that all properties of the file remain the same. On non-Unix
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
164 systems, the original file is renamed and a new file is written. Only the
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
165 protection bits are set like the original file. However, this doesn't work
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
166 properly when working on an NFS-mounted file system where links and other
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
167 things exist. The only way to fix this in the current version is not
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
168 making a backup file, by ":set nobackup nowritebackup" |'writebackup'|
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
169
22
cc049b00ee70 updated for version 7.0014
vimboss
parents: 7
diff changeset
170 Q. I'm using Vim to edit a file on a Unix file server through Samba. When I
cc049b00ee70 updated for version 7.0014
vimboss
parents: 7
diff changeset
171 write the file, the owner of the file is changed. Why?
cc049b00ee70 updated for version 7.0014
vimboss
parents: 7
diff changeset
172 A. When writing a file Vim renames the original file, this is a backup (in
cc049b00ee70 updated for version 7.0014
vimboss
parents: 7
diff changeset
173 case writing the file fails halfway). Then the file is written as a new
cc049b00ee70 updated for version 7.0014
vimboss
parents: 7
diff changeset
174 file. Samba then gives it the default owner for the file system, which may
cc049b00ee70 updated for version 7.0014
vimboss
parents: 7
diff changeset
175 differ from the original owner.
cc049b00ee70 updated for version 7.0014
vimboss
parents: 7
diff changeset
176 To avoid this set the 'backupcopy' option to "yes". Vim will then make a
cc049b00ee70 updated for version 7.0014
vimboss
parents: 7
diff changeset
177 copy of the file for the backup, and overwrite the original file. The
cc049b00ee70 updated for version 7.0014
vimboss
parents: 7
diff changeset
178 owner isn't changed then.
cc049b00ee70 updated for version 7.0014
vimboss
parents: 7
diff changeset
179
7
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
180 Q. How do I get to see the output of ":make" while it's running?
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
181 A. Basically what you need is to put a tee program that will copy its input
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
182 (the output from make) to both stdout and to the errorfile. You can find a
1125
96cd8222a819 updated for version 7.1a
vimboss
parents: 874
diff changeset
183 copy of tee (and a number of other GNU tools) at
7
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
184 http://gnuwin32.sourceforge.net or http://unxutils.sourceforge.net
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
185 Alternatively, try the more recent Cygnus version of the GNU tools at
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
186 http://www.cygwin.com Other Unix-style tools for Win32 are listed at
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
187 http://directory.google.com/Top/Computers/Software/Operating_Systems/Unix/Win32/
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
188 When you do get a copy of tee, you'll need to add >
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
189 :set shellpipe=\|\ tee
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
190 < to your _vimrc.
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
191
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
192 Q. I'm storing files on a remote machine that works with VisionFS, and files
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
193 disappear!
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
194 A. VisionFS can't handle certain dot (.) three letter extension file names.
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
195 SCO declares this behavior required for backwards compatibility with 16bit
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
196 DOS/Windows environments. The two commands below demonstrate the behavior:
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
197 >
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
198 echo Hello > file.bat~
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
199 dir > file.bat
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
200 <
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
201 The result is that the "dir" command updates the "file.bat~" file, instead
237
73354c21f1e4 updated for version 7.0066
vimboss
parents: 22
diff changeset
202 of creating a new "file.bat" file. This same behavior is exhibited in Vim
7
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
203 when editing an existing file named "foo.bat" because the default behavior
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
204 of Vim is to create a temporary file with a '~' character appended to the
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
205 name. When the file is written, it winds up being deleted.
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
206
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
207 Solution: Add this command to your _vimrc file: >
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
208 :set backupext=.temporary
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
209
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
210 Q. How do I change the blink rate of the cursor?
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
211 A. You can't! This is a limitation of the NT console. NT 5.0 is reported to
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
212 be able to set the blink rate for all console windows at the same time.
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
213
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
214 *:!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
215 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
216 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
217 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
218 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
219 :!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
220 < 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
221 :!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
222 < 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
223 :!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
224 < 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
225 :!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
226 <
a3ea65af63cf patch 8.0.0501: on MS-Windows ":!start" does not work as expected
Christian Brabandt <cb@256bit.org>
parents: 10264
diff changeset
227 Using "start" stops Vim switching to another screen, opening a new console,
7
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
228 or waiting for the program to complete; it indicates that you are running a
1624
18ee39301b82 updated for version 7.2a
vimboss
parents: 1281
diff changeset
229 program that does not affect the files you are editing. Programs begun
7
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
230 with :!start do not get passed Vim's open file handles, which means they do
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
231 not have to be closed before Vim.
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
232 To avoid this special treatment, use ":! start".
2859
ce1dce2af2a3 updated for version 7.3.203
Bram Moolenaar <bram@vim.org>
parents: 2681
diff changeset
233 There are two optional arguments (see the next Q):
3513
1b584a6f446c Updated runtime files.
Bram Moolenaar <bram@vim.org>
parents: 3082
diff changeset
234 /min the window will be minimized
1b584a6f446c Updated runtime files.
Bram Moolenaar <bram@vim.org>
parents: 3082
diff changeset
235 /b no console window will be opened
3082
3502a7f991fc Updated runtime files.
Bram Moolenaar <bram@vim.org>
parents: 2908
diff changeset
236 You can use only one of these flags at a time. A second one will be
2859
ce1dce2af2a3 updated for version 7.3.203
Bram Moolenaar <bram@vim.org>
parents: 2681
diff changeset
237 treated as the start of the command.
ce1dce2af2a3 updated for version 7.3.203
Bram Moolenaar <bram@vim.org>
parents: 2681
diff changeset
238
ce1dce2af2a3 updated for version 7.3.203
Bram Moolenaar <bram@vim.org>
parents: 2681
diff changeset
239 Q. How do I avoid getting a window for programs that I run asynchronously?
3082
3502a7f991fc Updated runtime files.
Bram Moolenaar <bram@vim.org>
parents: 2908
diff changeset
240 A. You have two possible solutions depending on what you want:
2908
fd09a9c8468e Updated runtime files.
Bram Moolenaar <bram@vim.org>
parents: 2859
diff changeset
241 1) You may use the /min flag in order to run program in a minimized state
fd09a9c8468e Updated runtime files.
Bram Moolenaar <bram@vim.org>
parents: 2859
diff changeset
242 with no other changes. It will work equally for console and GUI
fd09a9c8468e Updated runtime files.
Bram Moolenaar <bram@vim.org>
parents: 2859
diff changeset
243 applications.
fd09a9c8468e Updated runtime files.
Bram Moolenaar <bram@vim.org>
parents: 2859
diff changeset
244 2) You can use the /b flag to run console applications without creating a
2859
ce1dce2af2a3 updated for version 7.3.203
Bram Moolenaar <bram@vim.org>
parents: 2681
diff changeset
245 console window for them (GUI applications are not affected). But you
2908
fd09a9c8468e Updated runtime files.
Bram Moolenaar <bram@vim.org>
parents: 2859
diff changeset
246 should use this flag only if the application you run doesn't require any
fd09a9c8468e Updated runtime files.
Bram Moolenaar <bram@vim.org>
parents: 2859
diff changeset
247 input. Otherwise it will get an EOF error because its input stream
3082
3502a7f991fc Updated runtime files.
Bram Moolenaar <bram@vim.org>
parents: 2908
diff changeset
248 (stdin) would be redirected to \\.\NUL (stdout and stderr too).
2859
ce1dce2af2a3 updated for version 7.3.203
Bram Moolenaar <bram@vim.org>
parents: 2681
diff changeset
249
ce1dce2af2a3 updated for version 7.3.203
Bram Moolenaar <bram@vim.org>
parents: 2681
diff changeset
250 Example for a console application, run Exuberant ctags: >
ce1dce2af2a3 updated for version 7.3.203
Bram Moolenaar <bram@vim.org>
parents: 2681
diff changeset
251 :!start /min ctags -R .
ce1dce2af2a3 updated for version 7.3.203
Bram Moolenaar <bram@vim.org>
parents: 2681
diff changeset
252 < When it has finished you should see file named "tags" in your current
ce1dce2af2a3 updated for version 7.3.203
Bram Moolenaar <bram@vim.org>
parents: 2681
diff changeset
253 directory. You should notice the window title blinking on your taskbar.
6180
6921742f396a Update runtime files.
Bram Moolenaar <bram@vim.org>
parents: 5400
diff changeset
254 This is more noticeable for commands that take longer.
2859
ce1dce2af2a3 updated for version 7.3.203
Bram Moolenaar <bram@vim.org>
parents: 2681
diff changeset
255 Now delete the "tags" file and run this command: >
ce1dce2af2a3 updated for version 7.3.203
Bram Moolenaar <bram@vim.org>
parents: 2681
diff changeset
256 :!start /b ctags -R .
ce1dce2af2a3 updated for version 7.3.203
Bram Moolenaar <bram@vim.org>
parents: 2681
diff changeset
257 < You should have the same "tags" file, but this time there will be no
ce1dce2af2a3 updated for version 7.3.203
Bram Moolenaar <bram@vim.org>
parents: 2681
diff changeset
258 blinking on the taskbar.
ce1dce2af2a3 updated for version 7.3.203
Bram Moolenaar <bram@vim.org>
parents: 2681
diff changeset
259 Example for a GUI application: >
ce1dce2af2a3 updated for version 7.3.203
Bram Moolenaar <bram@vim.org>
parents: 2681
diff changeset
260 :!start /min notepad
ce1dce2af2a3 updated for version 7.3.203
Bram Moolenaar <bram@vim.org>
parents: 2681
diff changeset
261 :!start /b notepad
ce1dce2af2a3 updated for version 7.3.203
Bram Moolenaar <bram@vim.org>
parents: 2681
diff changeset
262 < The first command runs notepad minimized and the second one runs it
ce1dce2af2a3 updated for version 7.3.203
Bram Moolenaar <bram@vim.org>
parents: 2681
diff changeset
263 normally.
7
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
264
6259
bd18da914be9 Update runtime files.
Bram Moolenaar <bram@vim.org>
parents: 6180
diff changeset
265 *windows-icon*
bd18da914be9 Update runtime files.
Bram Moolenaar <bram@vim.org>
parents: 6180
diff changeset
266 Q. I don't like the Vim icon, can I change it?
bd18da914be9 Update runtime files.
Bram Moolenaar <bram@vim.org>
parents: 6180
diff changeset
267 A. Yes, place your favorite icon in bitmaps/vim.ico in a directory of
bd18da914be9 Update runtime files.
Bram Moolenaar <bram@vim.org>
parents: 6180
diff changeset
268 'runtimepath'. For example ~/vimfiles/bitmaps/vim.ico.
bd18da914be9 Update runtime files.
Bram Moolenaar <bram@vim.org>
parents: 6180
diff changeset
269
bd18da914be9 Update runtime files.
Bram Moolenaar <bram@vim.org>
parents: 6180
diff changeset
270
7
3fc0f57ecb91 updated for version 7.0001
vimboss
parents:
diff changeset
271 vim:tw=78:fo=tcq2:ts=8:ft=help:norl: