> Well, I just tried the async grep idea with /b. The only problem (with > 7.3.434, so before any of the 'shellxquote' patches) is with the echo > statement in the command (which with /b is never displayed anyway). So > I retract my statement about redirection not working. Can we make the > help clearer? What exactly does that 'stdout and stderr' comment > actually mean?
This is "sub-shell". In unix meanings, \\.\NUL is /dev/null. (ls > output.txt) 2>&1> /dev/null As you know, ':!start' is imitation of 'start' command in cmd.exe. So I'm thinking vim's behavor should be same as cmd's one. If typing below in cmd.exe, it works correctly. C:\>start /b cmd /c echo 1vim_free | cscope -dl -f cscope.out | C:\cygwin-1.7\bin\sed --regexp-extended -e "s/(\S+) (\S+) ([0-9]+)/\1:\3 \2 I hope that vim should get same result. And I'm thinking :help is enough to understand behavior currently. Thanks. -- 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
