There are other factors which are right there in the help: - job_start() returns a Job object and doesn't wait for the job to finish - system() waits for the external command to finish and returns its full stdout output as a string.
I don't know Vim job control really well, but I seem to understand that in order to compare system() timing and job control timing you would have to set up callbacks to gather any output from the channel, and a callback to be called when the job ends (it may still write to stdout after it exits), and measure the time from just before job_start() to just after making sure that all output has been collected and that the job has ended. You might even, for testing purposes, try to write a System() user function to invoke the argument as a job and return its output as a string, with the disadvantage that you would completely lose job control asynchronism. But it would allow you a better comparison, namely between old-fashioned system() and this new job-control-based System(). Best regards, Tony. -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
