Mercurial > vim

comparison runtime/doc/os_win32.txt @ 2908:fd09a9c8468e

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Updated runtime files.
author Bram Moolenaar <bram@vim.org>
date Sun, 19 Jun 2011 05:09:16 +0200
parents ce1dce2af2a3
children 3502a7f991fc
comparison
equal deleted inserted replaced
2907:ea75da0af64d 2908:fd09a9c8468e
1 *os_win32.txt* For Vim version 7.3. Last change: 2010 Dec 19 1 *os_win32.txt* For Vim version 7.3. Last change: 2011 May 28
2 2
3 3
4 VIM REFERENCE MANUAL by George Reilly 4 VIM REFERENCE MANUAL by George Reilly
5 5
6 6
319 You can only one of these flags at a time. A second second one will be 319 You can only one of these flags at a time. A second second one will be
320 treated as the start of the command. 320 treated as the start of the command.
321 321
322 Q. How do I avoid getting a window for programs that I run asynchronously? 322 Q. How do I avoid getting a window for programs that I run asynchronously?
323 A. You have two possible solutions depending on what exactly do you want: 323 A. You have two possible solutions depending on what exactly do you want:
324 1) You may use the /min flag that would run program in minimized state with 324 1) You may use the /min flag in order to run program in a minimized state
325 no other changes. It will work equally for console and GUI applications. 325 with no other changes. It will work equally for console and GUI
326 2) You can use /b flag to run console applications without creating a 326 applications.
327 2) You can use the /b flag to run console applications without creating a
327 console window for them (GUI applications are not affected). But you 328 console window for them (GUI applications are not affected). But you
328 should use this flag only if application you run doesn't require any 329 should use this flag only if the application you run doesn't require any
329 input. Otherwise it will get an EOF error because it's input stream 330 input. Otherwise it will get an EOF error because its input stream
330 (stdin) would be redirected to \\.\NUL (stdour and stderr too). 331 (stdin) would be redirected to \\.\NUL (stdoud and stderr too).
331 332
332 Example for a console application, run Exuberant ctags: > 333 Example for a console application, run Exuberant ctags: >
333 :!start /min ctags -R . 334 :!start /min ctags -R .
334 < When it has finished you should see file named "tags" in your current 335 < When it has finished you should see file named "tags" in your current
335 directory. You should notice the window title blinking on your taskbar. 336 directory. You should notice the window title blinking on your taskbar.