I noticed a few typos in the help text, as follows (please read this
using a fixed-width font):
On 25/05/11 17:06, Bram Moolenaar wrote:
Patch 7.3.203
Problem: MS-Windows: Can't run an external command without a console window.
Solution: Support ":!start /b cmd". (Xaizek)
Files: runtime/doc/os_win32.txt, src/os_win32.c
*** ../mercurial/vim73/runtime/doc/os_win32.txt 2011-01-08 16:05:50.000000000
+0100
--- runtime/doc/os_win32.txt 2011-05-25 17:04:58.000000000 +0200
***************
*** 313,319 ****
with :!start do not get passed Vim's open file handles, which means they
do
not have to be closed before Vim.
To avoid this special treatment, use ":! start".
! The optional "/min" argument causes the window to be minimized.
Q. I'm using Win32s, and when I try to run an external command like "make",
Vim doesn't wait for it to finish! Help!
--- 313,348 ----
with :!start do not get passed Vim's open file handles, which means they
do
not have to be closed before Vim.
To avoid this special treatment, use ":! start".
! There are two optional arguments (see the next Q):
! /min the window will be minimized.
! /b" no console window will be opened
! You can only one of these flags at a time. A second second one will be
! treated as the start of the command.
!
! Q. How do I avoid getting a window for programs that I run asynchronously?
! A. You have two possible solutions depending on what exactly do you want:
! 1) You may use the /min flag that would run program in minimized state with
--------------------------------------------------^ the
or better: ------------------------ ^^^^^^^^^^^^^^^^^^^^^^ [in order] to
run the program ("in order" is optional here).
! no other changes. It will work equally for console and GUI applications.
! 2) You can use /b flag to run console applications without creating a
---------------------^ the
! console window for them (GUI applications are not affected). But you
! should use this flag only if application you run doesn't require any
--------------------------------------^ the
! input. Otherwise it will get an EOF error because it's input stream
-------------------------------------------------------------^^^^ its
! (stdin) would be redirected to \\.\NUL (stdour and stderr too).
--------------------------------------------------^^^^^^ stdout
!
! Example for a console application, run Exuberant ctags:>
! :!start /min ctags -R .
!< When it has finished you should see file named "tags" in your current
! directory. You should notice the window title blinking on your taskbar.
! This is more noticable for commands that take longer.
! Now delete the "tags" file and run this command:>
! :!start /b ctags -R .
!< You should have the same "tags" file, but this time there will be no
! blinking on the taskbar.
! Example for a GUI application:>
! :!start /min notepad
! :!start /b notepad
!< The first command runs notepad minimized and the second one runs it
! normally.
Q. I'm using Win32s, and when I try to run an external command like "make",
Vim doesn't wait for it to finish! Help!
[...]
The first three seems to indicate that the patch was written by someone
whose native language doesn't use a definite article.
The fourth is a frequent error committed by even some native English
speakers, even though there is a simple mnemonic trick for it:
(with apostrophe) *it's* = *it is*
(without) *its* foobar = the foobar *of it*
The last one is a simple miskeying, which comes from the fact that on
most non-Dvorak Latin keyboards, the R and T keys are next to each other.
Best regards,
Tony.
--
Romeo wasn't bilked in a day.
-- Walt Kelly, "Ten Ever-Lovin' Blue-Eyed Years With
Pogo"
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
