Skip to content

Commit

Permalink
Bug fix: Updated instructions to match new execute() implementation
Browse files Browse the repository at this point in the history
  • Loading branch information
xolox committed Jun 14, 2010
1 parent 364ceee commit 2cc68db
Showing 1 changed file with 8 additions and 8 deletions.
16 changes: 8 additions & 8 deletions README.md
Expand Up @@ -65,16 +65,16 @@ testing the three functions as follows from inside Vim:

3. (Windows only) Execute the following command:

:call xolox#shell#execute('vimrun')
:call xolox#shell#execute('vimrun', 0)

Immediately after executing this command Vim should respond to input again
because `execute()` doesn't wait for the external command to finish. Also no
command prompt window should have been created, which means `vimrun.exe` is
running completely invisible in the background. Please verify this: Open the
Windows task manager by pressing `Control-Shift-Escape` and check that the
process `vimrun.exe` is listed in the processes tab. If you don't see the
problem this is solving, try executing `vimrun.exe` using Vim's built-in
`system()` function instead:
because `execute()` doesn't wait for the external command to finish when the
second argument is false. Also no command prompt window should have been
created, which means `vimrun.exe` is running completely invisible in the
background. Please verify this: Open the Windows task manager by pressing
`Control-Shift-Escape` and check that the process `vimrun.exe` is listed in
the processes tab. If you don't see the problem this is solving, try
executing `vimrun.exe` using Vim's built-in `system()` function instead:

:call system('vimrun')

Expand Down

0 comments on commit 2cc68db

Please sign in to comment.