On Feb 22, 9:28 am, Ben Fritz <[email protected]> wrote: > Second, I'm not sure why it would ever work with /b. :help :!start > says: > > 2) You can use the /b flag to run console applications without > creating a > console window for them (GUI applications are not affected). But > you > should use this flag only if the application you run doesn't > require any > input. Otherwise it will get an EOF error because its input > stream > (stdin) would be redirected to \\.\NUL (stdout and stderr too). > > I've always taken the "stdout and stderr too" bit to mean that I > cannot redirect output to a file if I use /b. Is this not the case? > Have I just been interpreting it wrong even since /b was introduced? > Or maybe this restriction was just something that needed some code to > overcome? > > One > reasonhttp://vim.wikia.com/wiki/Execute_external_programs_asynchronously_un... > uses /min instead of /b for the extended "async grep" example is to > allow the redirection to work. Does it work with /b if we properly > escape things, potentially using the latest patch?
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? -- 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
