Mercurial > vim
annotate runtime/doc/gui_w32.txt @ 20552:74e3316c1d5a
Update runtime files
Commit: https://github.com/vim/vim/commit/388a5d4f20b4b64341d1604aa238cab85827b892
Author: Bram Moolenaar <Bram@vim.org>
Date: Tue May 26 21:20:45 2020 +0200
Update runtime files
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Tue, 26 May 2020 21:30:04 +0200 |
parents | 1908e92b02fd |
children | 1b345fb68ae3 |
rev | line source |
---|---|
19813 | 1 *gui_w32.txt* For Vim version 8.2. Last change: 2020 Mar 25 |
7 | 2 |
3 | |
4 VIM REFERENCE MANUAL by Bram Moolenaar | |
5 | |
6 | |
7 Vim's Win32 Graphical User Interface *gui-w32* *win32-gui* | |
8 | |
9 1. Starting the GUI |gui-w32-start| | |
10 2. Vim as default editor |vim-default-editor| | |
11 3. Using the clipboard |gui-clipboard| | |
12 4. Shell Commands |gui-shell-win32| | |
13 5. Special colors |win32-colors| | |
14 6. Windows dialogs & browsers |gui-w32-dialogs| | |
15 7. Command line arguments |gui-w32-cmdargs| | |
16 8. Various |gui-w32-various| | |
17 | |
18 Other relevant documentation: | |
19 |gui.txt| For generic items of the GUI. | |
4098 | 20 |os_win32.txt| For Win32 specific items. |
7 | 21 |
22 | |
23 ============================================================================== | |
24 1. Starting the GUI *gui-w32-start* | |
25 | |
26 The Win32 GUI version of Vim will always start the GUI, no matter how you | |
27 start it or what it's called. | |
28 | |
29 The GUI will always run in the Windows subsystem. Mostly shells automatically | |
30 return with a command prompt after starting gvim. If not, you should use the | |
31 "start" command: > | |
32 start gvim [options] file .. | |
16451
7ae2396cef62
patch 8.1.1230: a lot of code is shared between vim.exe and gvim.exe
Bram Moolenaar <Bram@vim.org>
parents:
14421
diff
changeset
|
33 < *E988* |
7ae2396cef62
patch 8.1.1230: a lot of code is shared between vim.exe and gvim.exe
Bram Moolenaar <Bram@vim.org>
parents:
14421
diff
changeset
|
34 The console version with the |-g| option may also start the GUI by executing |
7ae2396cef62
patch 8.1.1230: a lot of code is shared between vim.exe and gvim.exe
Bram Moolenaar <Bram@vim.org>
parents:
14421
diff
changeset
|
35 gvim.exe: > |
7ae2396cef62
patch 8.1.1230: a lot of code is shared between vim.exe and gvim.exe
Bram Moolenaar <Bram@vim.org>
parents:
14421
diff
changeset
|
36 vim -g [options] file .. |
7ae2396cef62
patch 8.1.1230: a lot of code is shared between vim.exe and gvim.exe
Bram Moolenaar <Bram@vim.org>
parents:
14421
diff
changeset
|
37 To make this work, gvim.exe must exist in the same directory as the vim.exe, |
7ae2396cef62
patch 8.1.1230: a lot of code is shared between vim.exe and gvim.exe
Bram Moolenaar <Bram@vim.org>
parents:
14421
diff
changeset
|
38 and this feature must be enabled at compile time. |
7ae2396cef62
patch 8.1.1230: a lot of code is shared between vim.exe and gvim.exe
Bram Moolenaar <Bram@vim.org>
parents:
14421
diff
changeset
|
39 |
7ae2396cef62
patch 8.1.1230: a lot of code is shared between vim.exe and gvim.exe
Bram Moolenaar <Bram@vim.org>
parents:
14421
diff
changeset
|
40 One may also use `:gui` from the console version. However, this is an |
7ae2396cef62
patch 8.1.1230: a lot of code is shared between vim.exe and gvim.exe
Bram Moolenaar <Bram@vim.org>
parents:
14421
diff
changeset
|
41 experimental feature and this feature must be enabled at compile time. |
7ae2396cef62
patch 8.1.1230: a lot of code is shared between vim.exe and gvim.exe
Bram Moolenaar <Bram@vim.org>
parents:
14421
diff
changeset
|
42 It uses a session file to recreate the current state of the console Vim in the |
7ae2396cef62
patch 8.1.1230: a lot of code is shared between vim.exe and gvim.exe
Bram Moolenaar <Bram@vim.org>
parents:
14421
diff
changeset
|
43 GUI Vim. |
7 | 44 |
45 Note: All fonts (bold, italic) must be of the same size!!! If you don't do | |
46 this, text will disappear or mess up the display. Vim does not check the font | |
47 sizes. It's the size in screen pixels that must be the same. Note that some | |
48 fonts that have the same point size don't have the same pixel size! | |
49 Additionally, the positioning of the fonts must be the same (ascent and | |
50 descent). | |
51 | |
52 The Win32 GUI has an extra menu item: "Edit/Select Font". It brings up the | |
53 standard Windows font selector. | |
54 | |
55 Setting the menu height doesn't work for the Win32 GUI. | |
56 | |
57 *gui-win32-maximized* | |
58 If you want Vim to start with a maximized window, add this command to your | |
59 vimrc or gvimrc file: > | |
60 au GUIEnter * simalt ~x | |
61 < | |
1376 | 62 |
63 Using Vim as a plugin *gui-w32-windowid* | |
64 | |
65 When gvim starts up normally, it creates its own top level window. If you | |
66 pass Vim the command-line option |--windowid| with a decimal or hexadecimal | |
67 value, Vim will create a window that is a child of the window with the given | |
68 ID. This enables Vim to act as a plugin in another application. This really | |
69 is a programmer's interface, and is of no use without a supporting application | |
70 to spawn Vim correctly. | |
71 | |
7 | 72 ============================================================================== |
73 2. Vim as default editor *vim-default-editor* | |
74 | |
75 To set Vim as the default editor for a file type: | |
76 1. Start a Windows Explorer | |
236 | 77 2. Choose View/Options -> File Types |
7 | 78 3. Select the path to gvim for every file type that you want to use it for. |
79 (you can also use three spaces in the file type field, for files without an | |
80 extension). | |
81 In the "open" action, use: > | |
82 gvim "%1" | |
83 < The quotes are required for using file names with embedded spaces. | |
84 You can also use this: > | |
85 gvim "%L" | |
86 < This should avoid short (8.3 character) file names in some situations. But | |
87 I'm not sure if this works everywhere. | |
88 | |
89 When you open a file in Vim by double clicking it, Vim changes to that | |
90 file's directory. | |
91 | |
92 If you want Vim to start full-screen, use this for the Open action: > | |
93 gvim -c "simalt ~x" "%1" | |
94 | |
95 Another method, which also works when you put Vim in another directory (e.g., | |
96 when you have got a new version): | |
97 1. select a file you want to use Vim with | |
98 2. <Shift-F10> | |
99 3. select "Open With..." menu entry | |
100 4. click "Other..." | |
101 5. browse to the (new) location of Vim and click "Open" | |
102 6. make "Always Use this program..." checked | |
103 7. <OK> | |
104 | |
105 *send-to-menu* *sendto* | |
106 You can also install Vim in the "Send To" menu: | |
107 1. Start a Windows Explorer | |
108 2. Navigate to your sendto directory: | |
10264
c036c0f636d5
commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
109 Windows XP: C:\Documents and Settings\%user%\SendTo |
c036c0f636d5
commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
110 Windows Vista: C:\Users\%user%\AppData\Roaming\Microsoft\Windows\SendTo . |
7 | 111 3. Right-click in the file pane and select New->Shortcut |
112 4. Follow the shortcut wizard, using the full path to VIM/GVIM. | |
113 | |
114 When you 'send a file to Vim', Vim changes to that file's directory. Note, | |
19116 | 115 however, that any long directory names will appear in their short (MS-DOS) |
116 form on some Windows versions. This is a limitation of the Windows "Send To" | |
117 mechanism. | |
7 | 118 |
119 *notepad* | |
120 You could replace notepad.exe with gvim.exe, but that has a few side effects. | |
121 Some programs rely on notepad arguments, which are not recognized by Vim. For | |
122 example "notepad -p" is used by some applications to print a file. It's | |
123 better to leave notepad where it is and use another way to start Vim. | |
124 | |
125 *win32-popup-menu* | |
126 A more drastic approach is to install an "Edit with Vim" entry in the popup | |
127 menu for the right mouse button. With this you can edit any file with Vim. | |
128 | |
129 This can co-exist with the file associations mentioned above. The difference | |
130 is that the file associations will make starting Vim the default action. With | |
131 the "Edit with Vim" menu entry you can keep the existing file association for | |
132 double clicking on the file, and edit the file with Vim when you want. For | |
133 example, you can associate "*.mak" with your make program. You can execute | |
134 the makefile by double clicking it and use the "Edit with Vim" entry to edit | |
135 the makefile. | |
136 | |
137 You can select any files and right-click to see a menu option called "Edit | |
1668 | 138 with gvim". Choosing this menu option will invoke gvim with the file you have |
7 | 139 selected. If you select multiple files, you will find two gvim-related menu |
140 options: | |
141 "Edit with multiple gvims" -- one gvim for each file in the selection | |
142 "Edit with single gvim" -- one gvim for all the files in the selection | |
143 And if there already is a gvim running: | |
144 "Edit with existing gvim" -- edit the file with the running gvim | |
145 | |
3082 | 146 The "edit with existing Vim" entries can be disabled by adding an entry in the |
147 registry under HKLM\Software\Vim\Gvim, named DisableEditWithExisting, and with | |
148 any value. | |
7 | 149 *install-registry* |
150 You can add the "Edit with Vim" menu entry in an easy way by using the | |
151 "install.exe" program. It will add several registry entries for you. | |
152 | |
153 You can also do this by hand. This is complicated! Use the install.exe if | |
154 you can. | |
155 | |
156 1. Start the registry editor with "regedit". | |
157 2. Add these keys: | |
158 key value name value ~ | |
159 HKEY_CLASSES_ROOT\CLSID\{51EEE242-AD87-11d3-9C1E-0090278BBD99} | |
160 {default} Vim Shell Extension | |
161 HKEY_CLASSES_ROOT\CLSID\{51EEE242-AD87-11d3-9C1E-0090278BBD99}\InProcServer32 | |
162 {default} {path}\gvimext.dll | |
163 ThreadingModel Apartment | |
164 HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers\gvim | |
165 {default} {51EEE242-AD87-11d3-9C1E-0090278BBD99} | |
166 HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved | |
167 {51EEE242-AD87-11d3-9C1E-0090278BBD99} | |
168 Vim Shell Extension | |
169 HKEY_LOCAL_MACHINE\Software\Vim\Gvim | |
170 path {path}\gvim.exe | |
19116 | 171 HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\vim 8.2 |
172 DisplayName Vim 8.2: Edit with Vim popup menu entry | |
18182
9b6bfce90778
patch 8.1.2086: missing a few changes for the renamed files
Bram Moolenaar <Bram@vim.org>
parents:
16553
diff
changeset
|
173 UninstallString {path}\uninstall.exe |
7 | 174 |
175 Replace {path} with the path that leads to the executable. | |
176 Don't type {default}, this is the value for the key itself. | |
177 | |
178 To remove "Edit with Vim" from the popup menu, just remove the registry | |
18182
9b6bfce90778
patch 8.1.2086: missing a few changes for the renamed files
Bram Moolenaar <Bram@vim.org>
parents:
16553
diff
changeset
|
179 entries mentioned above. The "uninstall.exe" program can do this for you. |
9b6bfce90778
patch 8.1.2086: missing a few changes for the renamed files
Bram Moolenaar <Bram@vim.org>
parents:
16553
diff
changeset
|
180 You can also use the entry in the Windows standard "Add/Remove Programs" list. |
7 | 181 |
182 If you notice that this entry overrules other file type associations, set | |
183 those associations again by hand (using Windows Explorer, see above). This | |
184 only seems to happen on some Windows NT versions (Windows bug?). Procedure: | |
185 1. Find the name of the file type. This can be done by starting the registry | |
186 editor, and searching for the extension in \\HKEY_CLASSES_ROOT | |
187 2. In a Windows Explorer, use View/Options/File Types. Search for the file | |
188 type in the list and click "Edit". In the actions list, you can select on | |
189 to be used as the default (normally the "open" action) and click on the | |
190 "Set Default" button. | |
191 | |
192 | |
193 Vim in the "Open With..." context menu *win32-open-with-menu* | |
194 | |
195 If you use the Vim install program you have the choice to add Vim to the "Open | |
196 With..." menu. This means you can use Vim to edit many files. Not every file | |
197 (for unclear reasons...), thus the "Edit with Vim" menu entry is still useful. | |
198 | |
199 One reason to add this is to be able to edit HTML files directly from Internet | |
200 Explorer. To enable this use the "Tools" menu, "Internet Options..." entry. | |
201 In the dialog select the "Programs" tab and select Vim in the "HTML editor" | |
19968 | 202 choice. If it's not there then installing didn't work properly. |
7 | 203 |
204 Doing this manually can be done with this script: | |
205 | |
206 ---------------------------------------------------------- | |
207 REGEDIT4 | |
208 | |
209 [HKEY_CLASSES_ROOT\Applications\gvim.exe] | |
210 | |
211 [HKEY_CLASSES_ROOT\Applications\gvim.exe\shell] | |
212 | |
213 [HKEY_CLASSES_ROOT\Applications\gvim.exe\shell\edit] | |
214 | |
215 [HKEY_CLASSES_ROOT\Applications\gvim.exe\shell\edit\command] | |
19116 | 216 @="c:\\vim\\vim82\\gvim.exe \"%1\"" |
7 | 217 |
218 [HKEY_CLASSES_ROOT\.htm\OpenWithList\gvim.exe] | |
219 | |
220 [HKEY_CLASSES_ROOT\*\OpenWithList\gvim.exe] | |
221 | |
222 ---------------------------------------------------------- | |
223 | |
19116 | 224 Change the "c:\\vim\\vim82" bit to where gvim.exe is actually located. |
7 | 225 |
226 To uninstall this run the Vim uninstall program or manually delete the | |
227 registry entries with "regedit". | |
228 | |
229 ============================================================================== | |
230 3. Using the clipboard *gui-clipboard* | |
231 | |
232 Windows has a clipboard, where you can copy text to, and paste text from. Vim | |
233 supports this in several ways. For other systems see |gui-selections|. | |
234 | |
235 The "* register reflects the contents of the clipboard. |quotestar| | |
236 | |
237 When the "unnamed" string is included in the 'clipboard' option, the unnamed | |
238 register is the same. Thus you can yank to and paste from the clipboard | |
239 without prepending "* to commands. | |
240 | |
241 The 'a' flag in 'guioptions' is not included by default. This means that text | |
242 is only put on the clipboard when an operation is performed on it. Just | |
243 Visually selecting text doesn't put it on the clipboard. When the 'a' flag is | |
244 included, the text is copied to the clipboard even when it is not operated | |
245 upon. | |
246 | |
247 *mswin.vim* | |
248 To use the standard MS-Windows way of CTRL-X, CTRL-C and CTRL-V, use the | |
249 $VIMRUNTIME/mswin.vim script. You could add this line to your _vimrc file: > | |
250 source $VIMRUNTIME/mswin.vim | |
251 | |
252 Since CTRL-C is used to copy the text to the clipboard, it can't be used to | |
253 cancel an operation. Use CTRL-Break for that. | |
254 | |
1121 | 255 CTRL-Z is used for undo. This means you can't suspend Vim with this key, use |
256 |:suspend| instead (if it's supported at all). | |
81 | 257 |
167 | 258 *CTRL-V-alternative* *CTRL-Q* |
7 | 259 Since CTRL-V is used to paste, you can't use it to start a blockwise Visual |
260 selection. You can use CTRL-Q instead. You can also use CTRL-Q in Insert | |
261 mode and Command-line mode to get the old meaning of CTRL-V. But CTRL-Q | |
262 doesn't work for terminals when it's used for control flow. | |
263 | |
264 NOTE: The clipboard support still has a number of bugs. See |todo|. | |
265 | |
266 ============================================================================== | |
267 4. Shell Commands *gui-shell-win32* | |
268 | |
269 Vim uses another window for external commands, to make it possible to run any | |
270 command. The external command gets its own environment for running, just like | |
271 it was started from a DOS prompt. | |
272 | |
273 *win32-vimrun* | |
274 Executing an external command is done indirectly by the "vimrun" command. The | |
275 "vimrun.exe" must be in the path for this to work. Or it must be in the same | |
276 directory as the Vim executable. If "vimrun" cannot be found, the command is | |
277 executed directly, but then the DOS window closes immediately after the | |
278 external command has finished. | |
279 WARNING: If you close this window with the "X" button, and confirm the | |
280 question if you really want to kill the application, Vim may be killed too! | |
281 (This does not apply to commands run asynchronously with ":!start".) | |
282 | |
10264
c036c0f636d5
commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
283 The window in which the commands are executed will be the default you have set |
c036c0f636d5
commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
284 up for "Console" in Control Panel. |
7 | 285 |
286 *win32-!start* | |
287 Normally, Vim waits for a command to complete before continuing (this makes | |
288 sense for most shell commands which produce output for Vim to use). If you | |
289 want Vim to start a program and return immediately, you can use the following | |
10264
c036c0f636d5
commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
290 syntax: > |
2681 | 291 :!start [/min] {command} |
292 The optional "/min" causes the window to be minimized. | |
293 | |
7 | 294 ============================================================================== |
295 5. Special colors *win32-colors* | |
296 | |
297 On Win32, the normal DOS colors can be used. See |dos-colors|. | |
298 | |
299 Additionally the system configured colors can also be used. These are known | |
300 by the names Sys_XXX, where XXX is the appropriate system color name, from the | |
301 following list (see the Win32 documentation for full descriptions). Case is | |
10264
c036c0f636d5
commit https://github.com/vim/vim/commit/cea912af725c54f4727a0565e31661f6b29c6bb1
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
302 ignored. |
7 | 303 |
304 Sys_3DDKShadow Sys_3DFace Sys_BTNFace | |
305 Sys_3DHilight Sys_3DHighlight Sys_BTNHilight | |
306 Sys_BTNHighlight Sys_3DLight Sys_3DShadow | |
307 Sys_BTNShadow Sys_ActiveBorder Sys_ActiveCaption | |
308 Sys_AppWorkspace Sys_Background Sys_Desktop | |
309 Sys_BTNText Sys_CaptionText Sys_GrayText | |
310 Sys_Highlight Sys_HighlightText Sys_InactiveBorder | |
311 Sys_InactiveCaption Sys_InactiveCaptionText Sys_InfoBK | |
312 Sys_InfoText Sys_Menu Sys_MenuText | |
313 Sys_ScrollBar Sys_Window Sys_WindowFrame | |
314 Sys_WindowText | |
315 | |
316 Probably the most useful values are | |
317 Sys_Window Normal window background | |
318 Sys_WindowText Normal window text | |
319 Sys_Highlight Highlighted background | |
320 Sys_HighlightText Highlighted text | |
321 | |
322 These extra colors are also available: | |
323 Gray, Grey, LightYellow, SeaGreen, Orange, Purple, SlateBlue, Violet, | |
324 | |
325 *rgb.txt* | |
326 Additionally, colors defined by a "rgb.txt" file can be used. This file is | |
327 well known from X11. A few lines from it: > | |
328 | |
329 255 218 185 peach puff | |
330 205 133 63 peru | |
331 255 181 197 pink | |
332 | |
333 This shows the layout of the file: First the R, G and B value as a decimal | |
334 number, followed by the name of the color. The four fields are separated by | |
335 spaces. | |
336 | |
337 You can get an rgb.txt file from any X11 distribution. It is located in a | |
338 directory like "/usr/X11R6/lib/X11/". For Vim it must be located in the | |
339 $VIMRUNTIME directory. Thus the file can be found with "$VIMRUNTIME/rgb.txt". | |
340 | |
341 ============================================================================== | |
342 *gui-w32-dialogs* *dialog* | |
343 6. Windows dialogs & browsers | |
344 | |
345 The Win32 GUI can use familiar Windows components for some operations, as well | |
346 as the traditional interface shared with the console version. | |
347 | |
348 | |
349 6.1 Dialogs | |
350 | |
351 The dialogs displayed by the "confirm" family (i.e. the 'confirm' option, | |
352 |:confirm| command and |confirm()| function) are GUI-based rather than the | |
353 console-based ones used by other versions. The 'c' flag in 'guioptions' | |
354 changes this. | |
355 | |
356 | |
357 6.2 File Browsers | |
358 | |
359 When prepending ":browse" before file editing commands, a file requester is | |
360 used to allow you to select an existing file. See |:browse|. | |
361 | |
362 | |
363 6.3 Tearoff Menus | |
364 | |
365 The Win32 GUI emulates Motif's tear-off menus. At the top of each menu you | |
366 will see a small graphic "rip here" sign. Selecting it will cause a floating | |
367 window to be created with the same menu entries on it. The floating menu can | |
368 then be accessed just as if it was the original (including sub-menus), but | |
369 without having to go to the menu bar each time. | |
370 This is most useful if you find yourself using a command buried in a sub-menu | |
371 over and over again. | |
372 The tearoff menus can be positioned where you like, and always stay just above | |
236 | 373 the Main Vim window. You can get rid of them by closing them as usual; they |
7 | 374 also of course close when you exit Vim. |
375 | |
376 *:tearoff* *:te* | |
377 :te[aroff] {name} Tear-off the menu {name}. The menu named must have at | |
378 least one subentry, but need not appear on the | |
379 menu-bar (see |win32-hidden-menus|). | |
380 | |
381 Example: > | |
382 :tearoff File | |
383 will make the "File" menu (if there is one) appear as a tearoff menu. > | |
384 | |
385 :amenu ]Toolbar.Make :make<CR> | |
386 :tearoff ]Toolbar | |
387 This creates a floating menu that doesn't exist on the main menu-bar. | |
388 | |
389 Note that a menu that starts with ']' will not be displayed. | |
390 | |
391 ============================================================================== | |
392 7. Command line arguments *gui-w32-cmdargs* | |
393 | |
12756
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
10264
diff
changeset
|
394 Command line arguments behave the same way as with the console application, |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
10264
diff
changeset
|
395 see |win32-cmdargs|. |
7 | 396 |
397 ============================================================================== | |
398 8. Various *gui-w32-various* | |
399 | |
400 *gui-w32-printing* | |
401 The "File/Print" menu prints the text with syntax highlighting, see | |
402 |:hardcopy|. If you just want to print the raw text and have a default | |
403 printer installed this should also work: > | |
404 :w >>prn | |
405 | |
236 | 406 Vim supports a number of standard MS Windows features. Some of these are |
7 | 407 detailed elsewhere: see |'mouse'|, |win32-hidden-menus|. |
408 | |
409 *drag-n-drop-win32* | |
410 You can drag and drop one or more files into the Vim window, where they will | |
411 be opened as normal. See |drag-n-drop|. | |
412 | |
6476 | 413 *:simalt* *:sim* |
7 | 414 :sim[alt] {key} simulate pressing {key} while holding Alt pressed. |
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16451
diff
changeset
|
415 {only for Win32 versions} |
6476 | 416 Note: ":si" means ":s" with the "i" flag. |
7 | 417 |
418 Normally, Vim takes control of all Alt-<Key> combinations, to increase the | |
236 | 419 number of possible mappings. This clashes with the standard use of Alt as the |
7 | 420 key for accessing menus. |
421 The quick way of getting standard behavior is to set the 'winaltkeys' option | |
422 to "yes". This however prevents you from mapping Alt keys at all. | |
423 Another way is to set 'winaltkeys' to "menu". Menu shortcut keys are then | |
424 handled by windows, other ALT keys can be mapped. This doesn't allow a | |
425 dependency on the current state though. | |
426 To get round this, the :simalt command allows Vim (when 'winaltkeys' is not | |
236 | 427 "yes") to fake a Windows-style Alt keypress. You can use this to map Alt key |
7 | 428 combinations (or anything else for that matter) to produce standard Windows |
236 | 429 actions. Here are some examples: > |
7 | 430 |
431 :map <M-f> :simalt f<CR> | |
432 This makes Alt-F pop down the 'File' menu (with the stock Menu.vim) by | |
433 simulating the keystrokes Alt, F. > | |
434 :map <M-Space> :simalt ~<CR> | |
236 | 435 This maps Alt-Space to pop down the system menu for the Vim window. Note that |
7 | 436 ~ is used by simalt to represent the <Space> character. > |
437 :map <C-n> :simalt ~n<CR> | |
236 | 438 Maps Control-N to produce the keys Alt-Space followed by N. This minimizes the |
7 | 439 Vim window via the system menu. |
440 | |
1121 | 441 Note that the key changes depending on the language you are using. |
442 | |
7 | 443 *intellimouse-wheel-problems* |
444 When using the Intellimouse mouse wheel causes Vim to stop accepting input, go | |
445 to: | |
446 ControlPanel - Mouse - Wheel - UniversalScrolling - Exceptions | |
447 | |
448 And add gvim to the list of applications. This problem only appears to happen | |
449 with the Intellimouse driver 2.2 and when "Universal Scrolling" is turned on. | |
450 | |
3750 | 451 |
452 XPM support *w32-xpm-support* | |
453 | |
14347 | 454 GVim can be build on MS-Windows with support for XPM files. |+xpm_w32| |
3750 | 455 See the Make_mvc.mak file for instructions, search for XPM. |
456 | |
457 To try out if XPM support works do this: > | |
458 :help | |
19813 | 459 :let runtime = escape($VIMRUNTIME, ' \') |
460 :exe 'sign define vimxpm icon=' .. runtime .. '\\vim16x16.xpm' | |
461 :exe 'sign place 1 line=1 name=vimxpm file=' .. expand('%:p') | |
3750 | 462 < |
19813 | 463 You may need to get the vim16x16.xpm file from github: |
464 https://github.com/vim/vim/blob/master/runtime/vim16x16.xpm | |
465 | |
3750 | 466 |
14421 | 467 vim:tw=78:sw=4:ts=8:noet:ft=help:norl: |